Thanks for looking at this repo! Please answer the following questions:
Please clone this repo and run npm run start:
npm run start
> [email protected] start
...
✅✅✅ Hello, my name is Timmy
...
🚀🚀🚀 Hello, my name is Sally
I'm interested in a good explanation about why NodeJS is handling the some-package differently in each execution of some-app.
And for bonus points, give some examples where this behaviour is useful and where is can be unexpected / harmful.
And for even more bonus points, how can a package manager like npm or pnpm achieve the same behaviour?
- https://www.npmjs.com/package/@nymproject/sdk
- https://www.npmjs.com/package/@nymproject/sdk-full-fat
- https://www.npmjs.com/package/@nymproject/sdk-commonjs
- https://www.npmjs.com/package/@nymproject/sdk-commonjs-full-fat
Each of these packages is useful in a different situation. Please explain when you would use each of them and why.
And for bonus points, why would you need to use https://www.npmjs.com/package/@nymproject/sdk-nodejs and when wouldn't you use it and why?
Look at the packages above and explain when the following CSPs would cause errors and why:
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_eval_expressions
- https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_webassembly_execution
And for bonus points, when would you be likely to encounter these CSP errors when using Nym's SDK packages?
I'm interested when it is best to use each of the bundlers above and why. In particular, I'd like to know how each bundler handles Web Workers and WASM, with reference to the Nym packages above.
In the context of the packages below, why is the Web Transport API interesting?