Webpacker gets mad when using default locally when Node10 expected

Hi all! I’ll add more detail and attach an example repo, but posting now to get the ball rolling on this.

To reproduce

  1. Use nvm to select Node13
  2. Boot a rails app that was setup for Node10
  3. Boot webpack-dev-server

Expected behavior: Get a reasonable error message alerting you that you should use the node version of the app preferably with an appropriate link to how/where to do that.

Actual behavior: Super odd message about assets not being found, sometimes mentions mismatched SHAs.

1 Like

Thanks for two things:

  1. getting the ball rolling fast, in the spirit of this forum
  2. doing the work to follow up with a reproduction!