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
*Marco: issue with –eval, unflagging –experimental-strip-types would cause a breaking change in case Node.js was fed with invalid syntax.
38
+
*Created a PR to keep the current behavior and added explicit input types for typescript syntax
39
39
<https://github.com/nodejs/node/pull/56285>
40
-
This should make unflagging possible.
41
-
Before unflagging we should create some content on how to publish TypeScript packages, some part of it was done by the TypeScript team. It’s also important to document decision making about `node_modules`.
42
-
Augustin: should we mention in the guide, to publish as `esm` or `cjs` or both?
43
-
Marco: we should link back to Jakob article on js publishing article, it should be linked but more focused on the ts side rather than general.
44
-
Marco: The item on the issue about frontend metaframeworks is currently irrelevant because we don’t allow type stripping in node_modules so they still have to go through a transpilation step.
40
+
* This should make unflagging possible.
41
+
* Before unflagging we should create some content on how to publish TypeScript packages, some part of it was done by the TypeScript team. It’s also important to document decision making about `node_modules`.
42
+
*Augustin: should we mention in the guide, to publish as `esm` or `cjs` or both?
43
+
*Marco: we should link back to Jakob article on js publishing article, it should be linked but more focused on the ts side rather than general.
44
+
*Marco: The item on the issue about frontend metaframeworks is currently irrelevant because we don’t allow type stripping in node_modules so they still have to go through a transpilation step.
0 commit comments