Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider relaxing backwards compatibility stance #101

Open
guybedford opened this issue Aug 25, 2024 · 0 comments
Open

Consider relaxing backwards compatibility stance #101

guybedford opened this issue Aug 25, 2024 · 0 comments

Comments

@guybedford
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant