-
Notifications
You must be signed in to change notification settings - Fork 122
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
Initial submission to provide Production build support for Walt-explorer #170
Conversation
…sting "Development" build. It essentially addresses the requirement of the following story to some extent: ballercat#128 To execute production build, "build:prod" mode has been added to package.json (in ~/packages/walt-docs/) It reduces output JS file, explorer.js, by about 50% Following testings have been performed for this submission: - manually loading explorer.js file from /docs folder - npm test
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cd packages
git mv walt-docs walt-explorer
Please move the docs folder as it's not really documentation
packages/walt-docs/package.json
Outdated
@@ -7,6 +7,7 @@ | |||
"start": "webpack-dev-server -d --hot --inline", | |||
"start-container": "webpack-dev-server -d --hot --inline --host=$(hostname -I | xargs)", | |||
"build": "webpack && cp index.html explorer.js explorer.js.map walt.png ../../docs/", | |||
"build:prod": "cross-env NODE_ENV=production webpack && cp index.html explorer.js explorer.js.map walt.png ../../docs/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There isn't much of a point to keep both prod and dev build commands so let's just use build
for this, drop the old command entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had similar thoughts. Will do the changes now as you have suggested. Thanks!
- Renamed "walt-docs" to "walt-explorer" at ~/packages/ - Made "build" linked to production instead of having two similar naming builds [build, development] & [build:prod, production] in ~packages/walt-explorer/package.json
This submission supports "Production" build mode, in addition to, existing "Development" build. It essentially addresses the requirement of the following story to some extent:
#128
To execute production build, "build:prod" mode has been added to package.json (in ~/packages/walt-docs/)
It reduces output JS file, explorer.js, by about 50%
Following testings have been performed for this submission: