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
Just wanted to discuss some possible content changes to a recent blog post:
1. AMD
Webpack supports two standards for Module configuration: EcmaScript and CommonJS.
Even if it's unfashionable these days, webpack does support AMD module syntax. I think there is some value in including a brief example and explanation.
2. npm scripts
{"name": "my-webpack-demo",
...
"scripts": {"test": "echo \"Error: no test specified\" && exit 1","build": "./node_modules/webpack-cli/bin/webpack.js","watch": "./node_modules/webpack-cli/bin/webpack.js --watch"},
...
}
Thanks for your feedback! I agree that these are worth mentioning - I will provide an update to the article along with PR #34 which addresses your second point.
Just wanted to discuss some possible content changes to a recent blog post:
1. AMD
Even if it's unfashionable these days, webpack does support AMD module syntax. I think there is some value in including a brief example and explanation.
2.
npm
scriptsA major advantage to using
npm
scripts is that we can use the namespace given to the cli tools, even if they're installed locally. Because when evaluating scripts,npm
addsnode_modules/.bin/
to thePATH
environment variable. To highlight best practice, we can improve that snippet to read:The text was updated successfully, but these errors were encountered: