-
Notifications
You must be signed in to change notification settings - Fork 138
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
production build not working #11
Comments
It's a known issue which arises today, this repo depends on the Commenting Uglify plugin from webpack config will help the prod build to be successful. Tomorrow, I'll have a look at the UglifyJs2 repo and try to solve this. |
Cool, thanks ! 👍 |
(internal note)
|
i have same issue |
@Mahmoud-hassan87 i'm still collecting information on this topic, seems like the new of UglifyJS broke many things. Stay tuned. |
@theomathieubhvr @Mahmoud-hassan87 get the latest version and try to build. I temporarily commented the |
Thanks ! That's working now. I don't know what to do with this issue, renaming it or closing it ? I'll let you decide. |
Let's leave it because I could not reproduce it (using |
I solved this by forcing the Get the latest version of this repository, and remove |
build(webpack): update config Closes #11
* build(webpack): update config * docs(readme): update README Closes (#11)
* build(webpack): update config Closes #11
* build(webpack): update config * docs(readme): update README Closes #11
* build(webpack): update config Closes #11
* build(webpack): update config * docs(readme): update README Closes #11
I'm submitting a ... (check one with "x")
Current behavior
After a fresh git clone / npm install, I run
npm run build:universal-prod
I get this issue 4 times.
Then :
Expected/desired behavior
Build files ready for universal production server.
Minimal reproduction of the problem with instructions
npm run build:universal-prod
Please tell us about your environment:
Mac OS, yarn.
node --version
= 6.9.1Thanks !
PS : it might be that I don't completely understand how to run production. If so, I can create a PR modifying the readme.
The text was updated successfully, but these errors were encountered: