Skip to content
This repository has been archived by the owner on Sep 12, 2020. It is now read-only.

How to use react-toolbox? #19

Open
stewartellis opened this issue Mar 15, 2016 · 0 comments
Open

How to use react-toolbox? #19

stewartellis opened this issue Mar 15, 2016 · 0 comments

Comments

@stewartellis
Copy link

Hi, thanks for putting this together. While there are a pile of starter projects and react/redux boilerplate repos out there, my hope is to start with this one on a project as I'm interested in baking the security in as early as possible.

I've titled this issue exactly the same as this one in a different repo, as it's the exact same problem - I'm trying to implement react-toolbox and am getting lots of errors. @davezuko does a good job of documenting the required fixes for his repo. I tried a few things including adding...

webpackConfig.resolve = { extensions: ['', '.jsx', '.scss', '.js', '.json'], modulesDirectories: [ 'node_modules', path.resolve(__dirname, './node_modules') ] };

...to /build/webpack/development.js. This seemed to get rid of all the errors but one:

{ [Error: ENOENT: no such file or directory, open '.env'] errno: -2, code: 'ENOENT', syscall: 'open', path: '.env' }

Beyond that error, there is still the loading of the .scss to deal with.

I'm new to webpack and am guessing that the webpack config is chosen from the environment variable, but beyond that I'm unsure how to properly hook up react-toolbox. Putting the resolve block above in each deployment file doesn't seem very DRY for starters. Can you provide some guidance given the way this project's webpack configuration is set up?

Any help would be much appreciated.
Thanks

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant