-
-
Notifications
You must be signed in to change notification settings - Fork 486
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with resolving .bootstraprc file path #75
Comments
Same here when running in Docker container. We made some workarounds for this but a proper resolution would be great. |
I'd love to take a well tested and document PR for this, if you have one! |
same problem here with a symlinked node_modules folder. |
@vjpr, @phryneas, @damianlegawiec, @Animagani Should we have a separate PR? or put this into #90? CC: @pherris All, really appreciate the help. I'm jamming on some other projects at https://github.com/shakacode, most notably those with react-native along with [React on Rails](https://github.com/shakacode/react_on_rails/] and the associated tutorial. @alexfedoseev is super busy as well! |
@vjpr, @phryneas, @damianlegawiec, @Animagani: See #114. I've published 1.1.0-beta.1. I'm awaiting review comments and somebody to verify that the new build works. |
Hello,
I have an issue connected with resolving path to .bootstraprc file.
Background:
On CI server, before running build scripts I am symlinking node_modules from different directory. It let's me to save build time, as I don't have to install node_modules on each build (gitlab-ci is odd and currently it's not possible to save node_modules directory between builds).
Issue:
On build, bootstrap-loader tries to find .bootstraprc file in path /foo/bar/cache/.bootstraprc (node_modules are stored in /foo/bar/cache/node_modules, project is cloned to /foo/bar/builds/projectX and build is running there).
Possible solution:
I've changed bootstrap-loader/src/bootstrap.config.js file:
But I'm not sure if it doesn't break something else ;)
Other node-modules with their configurations in project root directory (eslint, babel) works correctly.
The text was updated successfully, but these errors were encountered: