Migrate from webpacker and nodejs v15 to shakapacker and nodejs v18 #412
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
for webpacker v6
Fix `Unknown Statement of type "ForOfStatement"`
webpacker v6 and webpack-dev-server v5 are incompatible
|
@unasuke Thank you!! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reason for Change
We use cfp-app for Kaigi on Rails, rails and web tech conference in Japan.
https://cfp.kaigionrails.org/
Changes
NODE_OPTIONS=--openssl-legacy-providerThis change is the first step in modernizing cfp-app frontend stack. We choose vite_rails or jsbundling-rails in the future...maybe.
NOTE: I confirmed the migrated app behavior roughly. However, I did not check that the whole feature migrated correctly.