blitz
blitz copied to clipboard
blitz export -o does not export to provided folder
What is the problem?
Blitz export does not output to correct folder provided in the options
run blitz build
before:
blitz export -o dist
blitz export -o dist/
blitz export --outdir=dist
blitz export --outdir=dist/
All of them continue to export to the 'out' folder.
Paste all your error logs here:
Loaded env from /Users/d/Documents/6. Code/I/H/.env.local
Loaded env from /Users/d/Documents/6. Code/I/H/.env.env
info - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
warn - Detected blitz.config.js, no exported configuration found. https://nextjs.org/docs/messages/empty-configuration
info - using build directory: /Users/d/Documents/6. Code/I/H/.next
info - Copying "static build" directory
info - No "exportPathMap" found in "blitz.config.js". Generating map from "./pages"
info - Launching 11 workers
info - Copying "public" directory
info - Exporting (4/4)
Export successful. Files written to /Users/d/Documents/6. Code/I/H/out
Paste all relevant code snippets here:
blitz export -o dist
blitz export -o dist/
blitz export --outdir=dist
blitz export --outdir=dist/
What are detailed steps to reproduce this?
- blitz new app
- blitz build
- blitz export -o dist
Run blitz -v
and paste the output here:
macOS Monterey | darwin-x64 | Node: v16.13.0
blitz: 0.45.3 (global)
blitz: 0.45.3 (local)
Package manager: npm
System:
OS: macOS 12.2.1
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 18.43 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
Yarn: Not Found
npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
Watchman: Not Found
npmPackages:
@prisma/client: Not Found
blitz: 0.45.3 => 0.45.3
prisma: Not Found
react: 18.0.0-beta-149b420f6-20211119 => 18.0.0-beta-149b420f6-20211119
react-dom: 18.0.0-alpha-5ca4b0433-20211020 => 18.0.0-alpha-5ca4b0433-20211020
typescript: ~4.5 => 4.5.5
Please include below any other applicable logs and screenshots that show your problem:
No response