nodejs-reference-architecture
nodejs-reference-architecture copied to clipboard
nodeshift
The Red Hat and IBM Node.js Reference architecture. The teams 'opinion' on what components our customers and internal teams should use when building Node.js applications and guidance for how to be su...
@lholmquist https://www.jfrog.com/confluence/display/JFROG/npm+Registry#npmRegistry-AutomaticallyRewritingExternalDependencies
#### Advanced Tips / Tricks * TODO section blurb about hoisting and nohoist for strategies * TODO section for yarn resolutions * TODO section for individually controlled scripts. Provide use...
References to non-Node specific processes would be useful as additional context/resources.
Reactive streams (mutiny in quarkus) provides very good abstraction for even streaming. We can consider introducing that as separate category: https://github.com/reactive-streams/reactive-streams-js For java: https://smallrye.io/smallrye-mutiny/index.html Apart from reactive streams spec we...
Discuss/figure out if there is a way to validate/automate generation of the file which lists the modules we should check with npcheck: https://github.com/nodeshift/nodejs-reference-architecture/blob/main/npcheck.json
As each reference architecture is crutial to start with versioning - draft, 0.1.0 versions and publish them using automation. This is better to be done at the beginning because without...
Since webpack was mentioned here: https://github.com/nodeshift/nodejs-reference-architecture/pull/13/commits/fafdabca6c29828e45a7a35054aad04896e1ce91#diff-249bf41df0377faeb8e9da6b15672163R17 I believe that makes sense to have some "bundler" section in docs [ also mentioning webpack ]
Research ideas for dynamic/file upload using express.js/s3 etc. See also: https://github.com/nodeshift/nodejs-reference-architecture/issues/9