You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can use the volta switch or bind node version, but there is no way to guarantee the std lib version. And I think it is time to let @types/node retire. So we can use something like @node/std version to guarantee the std function behavior in both node and typescript, and use different std version parts in the same project. And I think we should consider that some of the std libs should be consistent in both node and browser.
And I think contributing to a small project like @node/std can lower entry to contribute to node std. node project should focus on lower API and @node/std can focus on user API.
Deno's std lib is good, I think it is time to let node std evolve.
Further, if Node and Deno can have one std, that is my dream.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We can use the volta switch or bind node version, but there is no way to guarantee the std lib version. And I think it is time to let @types/node retire. So we can use something like @node/std version to guarantee the std function behavior in both node and typescript, and use different std version parts in the same project. And I think we should consider that some of the std libs should be consistent in both node and browser.
And I think contributing to a small project like @node/std can lower entry to contribute to node std. node project should focus on lower API and @node/std can focus on user API.
Deno's std lib is good, I think it is time to let node std evolve.
Further, if Node and Deno can have one std, that is my dream.
Beta Was this translation helpful? Give feedback.
All reactions