-
Notifications
You must be signed in to change notification settings - Fork 147
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
node production mode #94
Comments
Thanks, I'd love to accept a PR for this.
|
I did node production mode. For angular 1.X examples can be taken from /~https://github.com/darxx/AngularWorkshop/tree/step6 |
@darxx , can you send a PR? I'll help where I can |
Yes. After work I will try to figure it out. Now I`m thinking to use global.env and separate gulp.config.js part that is using module.exports = function () { And and var config = {
And now I`m getting 07 06 2016 15:34:03.353:INFO [karma]: Karma v0.13.22 server started at http://localhost:9876/ Remapping coverage to TypeScript format... At home I will have more time to figure it out. |
gulp build --exclude-source --prod |
<Have you checked issues section which may have your similar issue?>
Issue Overview
If You are running npm install --production
You don`t have all needed node module to make production build on linux agent.
If You make only npm install. You are installing all packages not needed for production. Like:
browser-sync
connect-history-api-fallback
Issue Description
gulp.config strongly banded to gulp.config.js
And no production logic is separated. If You are following best practice installing only node mode that are required for each environment.
Reproducables
npm install --production
gulp build --exclude-source
Information
The text was updated successfully, but these errors were encountered: