bin/webpack-dev-server and bin/webpack does not exists, upon following steps on the Getting Started guide

[KarlHeitmann]

Hi!

After following the steps here to get started, when I tried tu run bin/dev I got the following error

unknown command: bin/webpacker-dev-server
sh: bin/webpacker: No such file or directory

I checked the bin/ folder and this is what I've got: no webpacker* files:

The stack I'm using is:

1. Ruby version: 3.2.2
2. Rails version: 7.0.6
3. Webpacker version: ?? on package.json: webpack: 5
4: Shakapacker: 7.0.2
5. React on Rails version: 13.3.5

This is not the first time I ran with this issue. The first time I followed the getting started guide, I ran the command with the --strict flag. As told on the getting started guide. But upon running the 4th step command: rails generate react_on_rails:install I noticed this bug on the final message: The same command to run with HMR and without HMR:

NOTE:
I took a look at the source code and found this was fixed on commit: 86c327bf4efbd6c446502b12ad77fc1ecabeca0e 02/24/2023, and the --strictflag had me installedreact_on_rails version 13.3.0. Then I ran the bin/devcommand and the application crashed because it couldn't found neitherwebpackernorwebpacker-dev-server. So I went to another folder and run the commands described on the getting started guide again but without the --strictflag, and when the moment came to run thebin/devcommand it couldn't found thewebpacker` executable files. That's when I decided to open a new issue on the repository and came here.

Best

[ahangarha]

Sorry for the inconvenience.
We are about to make a new release for Shakapacker 7 support #1548.

You may wait for 2-3 more days otherwise, these are the options:

• manually update several files to match Shakapacker 7
• downgrade your Shakapacker to version 6 and run the installation process again

cc @justin808

[KarlHeitmann]

Sorry for the inconvenience. We are about to make a new release for Shakapacker 7 support #1548.

You may wait for 2-3 more days otherwise, these are the options:

* manually update several files to match Shakapacker 7

* downgrade your Shakapacker to version 6 and run the installation process again

cc @justin808

Thanks, but I am not in a hurry, I just was curious and wanted to use the tool and found the bug. I just wanted to mention it here in case it was not yet reported :)

[ahangarha]

Thanks again for sharing the issue with us, and sorry again for the inconvenience.