Is your proposal related to a problem?
I am the author of Quarkus Quinoa, a Quarkus extension to ease dev and deployment of NodeJS app on Quarkus (a Java Framework).
To allow a good development experience, Quarkus also have a live coding mode, when using the Quinoa extension, it also starts the Node live coding server (npm start) and proxy relevant requests to it (the opposite of setupProxy in RCA).
Currently, it's not possible to disable historyApiFallback on the dev server (react-scripts start). Because of this the dev server is not honoring 404 when a file is not found making it complex to detect if a file is actually served by the NodeJs server or if it's just a fallback.
The Quinoa extension also allow historyApiFallback as part of its routing so having it on the NodeJs server is not necessary.
Describe the solution you'd like
Have an environment variable to disable historyApiFallback. e.g. HISTORY_API_FALLBACK=false react-scripts start
Is your proposal related to a problem?
I am the author of Quarkus Quinoa, a Quarkus extension to ease dev and deployment of NodeJS app on Quarkus (a Java Framework).
To allow a good development experience, Quarkus also have a live coding mode, when using the Quinoa extension, it also starts the Node live coding server (
npm start) and proxy relevant requests to it (the opposite ofsetupProxyin RCA).Currently, it's not possible to disable
historyApiFallbackon the dev server (react-scripts start). Because of this the dev server is not honoring 404 when a file is not found making it complex to detect if a file is actually served by the NodeJs server or if it's just a fallback.The Quinoa extension also allow historyApiFallback as part of its routing so having it on the NodeJs server is not necessary.
Describe the solution you'd like
Have an environment variable to disable
historyApiFallback. e.g.HISTORY_API_FALLBACK=false react-scripts start