Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 'nodemon' and 'uglify' scripts? #148

Open
tripu opened this issue Jan 24, 2019 · 0 comments
Open

Merge 'nodemon' and 'uglify' scripts? #148

tripu opened this issue Jan 24, 2019 · 0 comments

Comments

@tripu
Copy link
Member

tripu commented Jan 24, 2019

ash-nazg/package.json

Lines 6 to 12 in fc19443

"watch-server": "nodemon -w server.js -w gh.js -w store.js -w log.js --exec 'npm run start'",
"build-js-debug": "browserify app.jsx --debug | exorcist public/js/app.js.map > public/js/app.js",
"build-js": "NODE_ENV=production browserify app.jsx | uglifyjs - -c warnings=false -m > public/js/app.js",
"XXXX old version watch-js": "nodemon -e jsx,js --watch app.jsx --watch ./components/ --watch ./application/ --watch ./stores/ --watch ./actions/ --exec 'npm run build-js'",
"watch-js": "watchify app.jsx --verbose --ignore-watch=\"**/node_modules/**\" --ignore-watch=\"**/public/**\" -o 'uglifyjs - -c warnings=false -m > public/js/app.js'",
"build-css": "cleancss -o public/css/app.min.css app.css",
"watch-css": "nodemon --ignore ./public/ -e css --exec 'npm run build-css'",

We're (optionally) using both nodemon and watchify during local development to monitor JS and CSS sources for changes, and rebuild automatically.

Can we simplify dependencies a bit by using just one of them for both types of assets; or by switching to a different module that is more generic and can detect changes to any source file?


cf w3c/midgard#25

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant