You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We install our yarn modules into a different directory from the default .node_modules/ in the project directory. This works, but the webpacker yarn integrity check fails, because the command that's executed assumes the default location. A different directory can be specified with yarn check --integrity --modules-folder <path>.
Incidentally, the reason as to why we do this is because we use Docker, and have a shared cache for bundled gems and node modules, but there may be other reasons as to why people would do this.
I propose either an environment config, or even just an environment variable, to be able to specify the modules folder used for the integrity check command.
I'd be more than happy to issue a pull request if you agree and let me know if you have a preference of a config option or environment variable.
Thanks!
The text was updated successfully, but these errors were encountered:
We install our yarn modules into a different directory from the default
.node_modules/
in the project directory. This works, but the webpacker yarn integrity check fails, because the command that's executed assumes the default location. A different directory can be specified withyarn check --integrity --modules-folder <path>
.Incidentally, the reason as to why we do this is because we use Docker, and have a shared cache for bundled gems and node modules, but there may be other reasons as to why people would do this.
I propose either an environment config, or even just an environment variable, to be able to specify the modules folder used for the integrity check command.
I'd be more than happy to issue a pull request if you agree and let me know if you have a preference of a config option or environment variable.
Thanks!
The text was updated successfully, but these errors were encountered: