Change output directory
See original GitHub issueI can’t seem to find a way to change where the resulting files are output. At the moment they are all put in webpack’s output.path
, but in my case this isn’t ideal. Is there any way to change this?
Many thanks
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Change the build output directory - Visual Studio (Windows)
To change the build output directory using the current .NET Project Designer · Right-click on the project node in Solution Explorer and select ......
Read more >visualstudio-docs/how-to-change-the-build-output-directory ...
To change the build output directory using the current .NET Project Designer · Right-click on the project node in Solution Explorer and select...
Read more >How can I change the output directory? - MiKTeX
You can use the option --output-directory=NAME to specify an alternative location for all output files. For example, you would run
Read more >How to change output directory for a target - xcode
Go to File -> Project Settings. · Click the Advanced button under Derived Data Location. Under build location select custom and choose your ......
Read more >How can I change the output folder of my webUI install? - Reddit
I'm using the windows HLKY webUI which is installed on my C drive, but I want to change the output directory to a...
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 FreeTop 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
Top GitHub Comments
It took a bit of effort for me to figure it out so I though I’ll provide my solution for the ones to come
@tombeers @PeterKottas I’ve documented the missing options in #48. I also updated the
context
implementation to be the same as file-loader. That said, file-loader has another optionoutputPath
which does something similar but not the same thing? @alex-ketch any idea what the difference exactly is?