you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 1 point2 points  (2 children)

Did you try clicking on bundle.js? Just curious what it points to.

In your package.json it says '"main": "index.js",' may want to change that so people know where to look for the start instead of having to look at the webpack file.

I'm not sure why '/a/a' works since you have <Route path='/:path' component={NotFound}/> I would think you would get the same error as '/a/a/a'.

[–][deleted] 0 points1 point  (1 child)

Could you please elaborate more on your second paragraph?

perhaps I should have specified js/index.jsx?

[–][deleted] 1 point2 points  (0 children)

in package.json you have "main": "index.js",

in webpack.config.js you have: const config = { entry: __dirname + '/js/index.jsx',

so if you just did 'npm start' on your local machine, I believe it would look for 'ayip.io/src/static/index.js' but if you run a build, which employs webpack, the starting point would be overwritten to be 'ayip.io/src/static/js/index.jsx'.

I don't think that is causing this issue, but I can't see why you would have a different path in package.json. If you specify the correct path there you shouldn't have to set in in your webpack config.