Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Broken `historyApiFallback`

See original GitHub issue

I can’t get my app to properly implement historyApiFallback the proxy gets in the way. Even if I hack at the spinjs source to disable the proxy I webpack can’t find anything other than the index.

Issue Analytics

State:
Created 6 years ago
Comments:15 (10 by maintainers)

Top GitHub Comments

1reaction

msaspencecommented, Nov 6, 2017

Yaaaas! Will have a proper play with this on my actual project this evening

Thanks man

0reactions

larixercommented, Nov 6, 2017

Great! No problems!

Top Results From Across the Web

webpack dev server Proxies break historyApiFallback #3859

This issue has been automatically marked as stale because it hasn't had any recent activity. It will be closed in 14 days if...

webpack-dev-server, historyApiFallback not working ...

It turns out that I am missing output.publicPath in webpack.config.js: output: { // must specified output.publicPath otherwise // devServer.

DevServer - webpack

This option is ignored for Node 15.0.0 and above, as spdy is broken for those versions. The dev server will ... historyApiFallback by...

historyApiFallback troubles with webpack-dev-server and ...

A blog post on the topic of: historyApiFallback troubles with webpack-dev-server and React Router.

validationerror: invalid options object. dev server has been ...

toLowerCase(), compress: true, contentBase: BUILD_DIR, disableHostCheck: true, historyApiFallback: { disableDotRule: true, } ... this line is broken: ...