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
When working on nodejs/node#54648 I noticed that the package API documentation has been documenting some opinionated patterns that some consider dangerous. I think instead of continue piling more opinionated patterns or bikeshed about them in the API docs, we should just move these into their own repository (similar to https://github.com/nodejs/node-addon-examples), with example folders containing the multi-file structures that they are describing, and maybe some links to the discussions about their pros and cons. This repository can be named package-examples, etc., and we can extend it to describe other patterns such as how TypeScript packages can configure themselves before being shipped to npm.
cc @nodejs/package-maintenance @nodejs/loaders @nodejs/tsc
The text was updated successfully, but these errors were encountered:
When working on nodejs/node#54648 I noticed that the package API documentation has been documenting some opinionated patterns that some consider dangerous. I think instead of continue piling more opinionated patterns or bikeshed about them in the API docs, we should just move these into their own repository (similar to https://github.com/nodejs/node-addon-examples), with example folders containing the multi-file structures that they are describing, and maybe some links to the discussions about their pros and cons. This repository can be named
package-examples
, etc., and we can extend it to describe other patterns such as how TypeScript packages can configure themselves before being shipped to npm.cc @nodejs/package-maintenance @nodejs/loaders @nodejs/tsc
The text was updated successfully, but these errors were encountered: