nodejs / nodejs/cjs-module-lexer
Consider relaxing backwards compatibility stance
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 262
- Forks
- 31
- Avg merge
- 9d 2h
- Merged PRs (30d)
- 5
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the README's Project Status section and review the repository's outstanding issues and pull requests, especially those involving additional syntax cases or require(esm) compatibility. The issue is done only when maintainers decide whether the backwards-compatibility stance should change and identify which proposals, if any, should proceed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100