Apply config when running dev server
See original GitHub issueIs your feature request related to a problem? Please describe. When running a dev server, config like rewrites, authorization are not applied.
Describe the solution you’d like Apply config even when running dev server
- staticwebapp.config.json in current directory:
swa start http://localhost:8080
- staticwebapp.config.json elsewhere:
swa start http://localhost:8080 --routes-location web
(or whatever the option is eventually named #175)
Config should apply to function app routes as well.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
DevServer - webpack
webpack-dev-server can be used to quickly develop an application. See the development guide to get started. This page describes the options that affect...
Read more >webpack-dev-server
Using this config webpack-dev-server will serve the static files in your public folder. It'll watch your source files for changes and when changes...
Read more >webpack-dev-server - npm
[options] Run the webpack dev server. Options: -c, --config <value...> Provide path to a webpack configuration file e.g. ./webpack.config.js. -- ...
Read more >webpack-dev-server two configs - node.js - Stack Overflow
You can use the config option to specify your custom config file. > webpack-dev-server --config /home/user/project/path_to_config_file.
Read more >Configuring Webpack 5 and webpack-dev-server on React
Test production configuration ... Run on your terminal “npm run build”: The “dist” folder was created with the compressed files which are ready...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hey @fgiuliani we are going to refactor the proxy implementation (in #186) and this change will be affected. So we’re gonna delay this feature for now.
This should be addressed in #208