Can we migrate from webpacker v5 to shakapacker immediately or should we upgrade webpacker v5 to v6? #531

madyarini · 2024-12-20T06:48:41Z

madyarini
Dec 20, 2024

Hi, I am trying to migrate from webpacker v5 to shakapacker,
reading the guide it seems to imply that I should upgrade webpacker v5 to webpacker 6.0.0.rc.6.
I am having an issue after I run bundle exec rails webpacker:install

% bundle exec rails webpacker:install
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:214: warning: previous definition of BUFSIZE was here
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:541: warning: previous definition of Socket was here
DEPRECATION WARNING: Sprockets method `register_engine` is deprecated.
Please register a mime type using `register_mime_type` then
use `register_compressor` or `register_transformer`.
https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors
 (called from <main> at /Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/skim-0.10.0/lib/skim/sprockets.rb:3)
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:66: warning: already initialized constant Net::ProtocRetryError
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:68: warning: previous definition of ProtocRetryError was here
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:206: warning: already initialized constant Net::BufferedIO::BUFSIZE
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:214: warning: previous definition of BUFSIZE was here
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/2.7.0/net/protocol.rb:503: warning: already initialized constant Net::NetPrivate::Socket
/Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:541: warning: previous definition of Socket was here
DEPRECATION WARNING: Sprockets method `register_engine` is deprecated.
Please register a mime type using `register_mime_type` then
use `register_compressor` or `register_transformer`.
https://github.com/rails/sprockets/blob/master/guides/extending_sprockets.md#supporting-all-versions-of-sprockets-in-processors
 (called from <main> at /Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/skim-0.10.0/lib/skim/sprockets.rb:3)
   identical  config/webpacker.yml
    conflict  package.json
Overwrite /Users/mariel/app/package.json? (enter "h" for help) [Ynaqdhm] Y
       force  package.json
Copying webpack core config
       exist  config/webpack
   identical  config/webpack/base.js
   identical  config/webpack/development.js
   identical  config/webpack/production.js
   identical  config/webpack/test.js
The packs app source directory already exists
       apply  /Users/mariel/.asdf/installs/ruby/2.7.6/lib/ruby/gems/2.7.0/gems/webpacker-6.0.0.rc.6/lib/install/binstubs.rb
  Copying binstubs
       exist    bin
   identical    bin/webpack
   identical    bin/webpack-dev-server
   identical    bin/yarn
   unchanged  .gitignore
Default application.html.erb is missing!
        Add <%= javascript_pack_tag "application" %> within the <head> tag in your custom layout.
Run bin/yarn during bin/setup
File unchanged! Either the supplied flag value not found or the content has already been inserted!  bin/setup
Add node_modules to the asset load path
   unchanged  config/initializers/assets.rb
Make note of webpack-dev-server exemption needed to csp
   unchanged  config/initializers/content_security_policy.rb
Installing all JavaScript dependencies [from prerelease rails/webpacker]
         run  yarn add @rails/webpacker@next from "."
yarn add v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Saved 1 new dependency.
info Direct dependencies
└─ @rails/[email protected]
info All dependencies
└─ @rails/[email protected]
✨  Done in 2.29s.
Installing webpack and webpack-cli as direct dependencies
         run  yarn add webpack@^5.53.0 webpack-cli@^4.8.0 from "."
yarn add v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
[3/4] 🔗  Linking dependencies...
[4/4] 🔨  Building fresh packages...
success Saved 0 new dependencies.
✨  Done in 0.64s.
Installing dev server for live reloading
         run  yarn add --dev webpack-dev-server @webpack-cli/serve from "."
yarn add v1.22.19
[1/4] 🔍  Resolving packages...
[2/4] 🚚  Fetching packages...
error [email protected]: The engine "node" is incompatible with this module. Expected version ">=18". Got "16.20.2"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
Webpacker installation failed 😭 See above for details.

it is expecting node 18 instead of node 16.20.2.
the reason why I want to migrate to shakapacker is because I can't update node 16.20.2 to node 17.
Node17 updated SSL provider, which introduced breaking changes. From V16 to V17, this causes 0308010C:digital envelope routines::unsupported errors during pre-compiling
I believe this is because the webpacker is using some old encryption algorithm somewhere, so after upgrading to Shakapacker I can upgrade my node from 16 to 17.
Please advise if I can migrate from webpacker v5 to shakapacker without upgrading webpacker v5 to v6?
Thanks

tomdracz · 2024-12-20T13:37:48Z

tomdracz
Dec 20, 2024
Collaborator

You should be able to update directly to whatever version you want, though going through RC was mentioned as the most step-by-step way to go about it.

The error you're seeing is most likely because webpack-dev-server v5 has dependency on open package that requires node 18 at least. You should be able to go around it by using webpack-dev-server v4 https://www.npmjs.com/package/webpack-dev-server/v/4.15.2

https://webpack.js.org/configuration/dev-server/

webpack-dev-server v5.0.0+ requires node >= v18.12.0, webpack >= v5.0.0 and webpack-cli >= v4.7.0, we recommend using the latest version.

Both Node 16 and 17 are now EOL so recommendation would be not to use either of them. Even Node 18 is coming to EOL next year so migrating to later versions is probably the way to go

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Can we migrate from webpacker v5 to shakapacker immediately or should we upgrade webpacker v5 to v6? #531

{{title}}

Replies: 1 comment

{{title}}

Select a reply

Can we migrate from webpacker v5 to shakapacker immediately or should we upgrade webpacker v5 to v6? #531

madyarini Dec 20, 2024

Replies: 1 comment

tomdracz Dec 20, 2024 Collaborator

madyarini
Dec 20, 2024

tomdracz
Dec 20, 2024
Collaborator