-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Move inline babel settings to .babelrc #291
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
Conversation
@Davidzhu001 Could you please give this branch a try and see if it fixed the production deployment issue for you? # in Gemfile
gem 'webpacker', github: 'gauravtiwari/webpacker', branch: 'babel bundle update webpacker
bundle exec rails webpacker:install
bundle exec rails webpacker:install:vue
RAILS_ENV=production bundle exec rails webpacker:compile |
ok, I will test it when I get back. |
hooray, it worked! @gauravtiwari And I deployed with Cap too. It works fine on both. |
Awesome 👏 thanks for testing out 🍰 |
@gauravtiwari Do you know why the same error showed up again? |
@Davidzhu001 which error? |
Could you please paste fresh logs and setup you are using? Also, when (something you added/removed) this started happening? |
can i share the code to you? @gauravtiwari . alone with the server access? |
Sure 👍 although not sure I can take a look straightaway. Would that be okay? |
Ahh, same uglify error. Have you tried setting |
|
yes that's correct 👍 |
@gauravtiwari Thanks it worked |
@Davidzhu001 So, this is the work around for now if you are using es6 code inside vue app. There are other options, but none of them are mature enough to use in production. |
@gauravtiwari ok, can we make a wiki page to show people the solutions? |
Perhaps, if you could make a quick PR to add the uglify documentation in README, that would be ace. @RavenXce wrote something here too - #306 (comment) |
Related to - #202
Fixes - #202 and #180 and #261