Just run into the same problem,
Not sure if its the right approach or not, but what i did to make it work was to
move the javascript folder to the assets folder, then in "assets/config/manifest.js " file added this:
Its 2 dots before /javascript
2 dots mean folder that is one level higher than the current folder.
If you are using VScode you can copy relative path by just right clicking the file whose path you want.
//= link_tree ../images
//= link_tree ../../javascript .js
//= link_tree ../../../vendor/javascript .js
//= link frontend.js
//= link frontend.css
//= link admin.css
//= link admin.js
//= link dashboard/application.css
//= link dashboard/application.js
So, you have to navigate to root folder of your app, and run manually this instruction, but specifying the application.js like this: ./app/javascript/application.js
I think the problem is that you used npm instead of yarn. This means that webpack cannot compile the code generated. By default, the files generated, in Procfile.dev, you have:
js: yarn build --watch
either install yarn or if u want to use npm change this to:
js: npm run build -- --watch
then run
npm install -D webpack-cli
the error should clear.
I have been experiencing this issue with Rails 7.0.4 on macOS Ventura 13.0.1.
When I create a new Rails project that needs assets to be compiled, I get an error that The asset "application.js" is not present in the asset pipeline. I am using ./bin/dev to run the app. Using rails server yields the same behaviour.
For some strange reason, however, if I create and run the project from /tmp, it works.
I’d be grateful for any thoughts on how to fix this.
I tried your approach and it worked fine. But after several attempts on trying to customize Bootstrap components I can’t even point to the right stylesheet, my app now points everything the build folder. Do you know if this could be related to your solution?