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
But, if we can backport fixes across Node.js releases, perhaps there is scope to allow a new phase of additional features, especially to match with the unflagging of require(esm) which represents a new step in Node.js compat behaviours.
I wanted to create this issue to open that discussion, and then to possibly consider some of the outstanding issues / PRs. I have limited time to work on these myself, but if there is a maintainer interested it could be worth considering.
The text was updated successfully, but these errors were encountered:
The stance in this repo, as described in the readme - https://github.com/nodejs/cjs-module-lexer?tab=readme-ov-file#project-status is that only bug fixes and syntax updates will be landed but not new syntax cases, for the reason of backwards compatibility.
But, if we can backport fixes across Node.js releases, perhaps there is scope to allow a new phase of additional features, especially to match with the unflagging of require(esm) which represents a new step in Node.js compat behaviours.
I wanted to create this issue to open that discussion, and then to possibly consider some of the outstanding issues / PRs. I have limited time to work on these myself, but if there is a maintainer interested it could be worth considering.
The text was updated successfully, but these errors were encountered: