Once the PR at nodejs/node#35249 lands, Node.js will have a dependency on the external project https://github.com/guybedford/cjs-module-lexer, which was created and will be maintained explicitly for this PR feature.
I expect to maintain this project for at least a few years, but that maintenance would be done always based on upstreaming. In addition there would be no plans to add features that would not be included in the Node.js implementation.
To enable all Node.js collaborators to be able to equally contribute to this repo I would like to propose transferring the repo into the Node.js organization. I would continue to be the primary developer on that project, but it would be a clearer distinction than it being some arbitrary third party project without any direct involvement.
The primary roadmap I see for the project is:
- General maintenance.
- Improve any detection cases that come up.
- Upstream the C implementation at some point (instead of the JS implementation) for a minor perf improvement.
- Upstream any bug fixes from es-module-lexer (the project this was forked from in the first place).
It would be great to hear what others think of this or if there are other suggestions for handling the process between these projects.
//cc @targos
Once the PR at nodejs/node#35249 lands, Node.js will have a dependency on the external project https://github.com/guybedford/cjs-module-lexer, which was created and will be maintained explicitly for this PR feature.
I expect to maintain this project for at least a few years, but that maintenance would be done always based on upstreaming. In addition there would be no plans to add features that would not be included in the Node.js implementation.
To enable all Node.js collaborators to be able to equally contribute to this repo I would like to propose transferring the repo into the Node.js organization. I would continue to be the primary developer on that project, but it would be a clearer distinction than it being some arbitrary third party project without any direct involvement.
The primary roadmap I see for the project is:
It would be great to hear what others think of this or if there are other suggestions for handling the process between these projects.
//cc @targos