RollupError: Invalid value for option "output.file"
Server ]
[ Server ] > server@0.0.0 bundle
[ Server ] > rollup --config --silent
[ Server ]
✅ --- Successfully completed npm install. ----------------------------------------
🐝 --- Setting up database... -----------------------------------------------------
[ Server!] [!] RollupError: Invalid value for option "output.file" - when building multiple chunks, the "output.dir" option must be used, not "output.file". To inline dynamic imports, set the "inlineDynamicImports" option.
Already did wasp clean && wasp start and rm -rf .wasp node_modules/ package-lock.json
What's wrong?6 Replies
Hi @NEROX. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Wohooo @NEROX, you just became a Waspeteer level 17!
----------------------
I'm sorry, but the knowledge sources do not contain specific information about the "RollupError: Invalid value for option 'output.file'" when building with Wasp, nor do they provide details about configuring Rollup or resolving this particular error in the Wasp context.
However, based on the general troubleshooting steps in the sources, you have already tried the recommended actions such as running wasp clean and removing .wasp and node_modules folders, then restarting with wasp start. These are the standard steps for resolving most build and compilation issues in Wasp projects, as seen in several support threads and issues.
If the problem persists after these steps, it may be related to a misconfiguration in the build process or a bug in the Wasp framework itself. Since there is no direct solution in the provided sources, I recommend:
- Double-checking that you are using a supported version of Wasp and Node.js.
- Ensuring you have not modified any internal Wasp or build configuration files, as changes there can cause unexpected errors.
- If you are using a custom Rollup config or have made changes to the build process, try reverting to the default setup.
- If the issue remains unresolved, consider opening a new issue on the Wasp GitHub repository with details about your environment and the error message, as this may be a bug or an unsupported scenario.
If you have more context (such as recent changes to your project or custom build steps), please share it, and I can look for more targeted advice in the sources.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?
@kapa.ai still happening after 3 wasp clean and etc
Let me check the knowledge base for you again. One moment! :books:
----------------------
I'm sorry, but the knowledge sources do not contain specific information about the "RollupError: Invalid value for option 'output.file'" in the context of Wasp, nor do they provide a direct solution for this error. You have already tried the standard troubleshooting steps recommended in the sources, such as running
wasp clean and deleting .wasp, node_modules, and package-lock.json, then restarting with wasp start—these are the main steps suggested for resolving most build issues in Wasp projects Discord: solutions for build errors.
Since the error persists after these steps, and there is no further guidance in the provided sources, it may be a bug or an unsupported scenario. At this point, the best course of action is to open an issue on the Wasp GitHub repository with details about your environment and the error message, as suggested in similar situations in the sources.
If you have made any custom changes to build configurations or are running Wasp inside another NPM project, that could also be a factor, as there are known issues with nested projects and dependency resolution Wasp apps inside NPM projects don't work.
Unfortunately, without more specific information in the knowledge sources, I can't provide a more targeted solution.
----------------------
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
----------------------
Sorry @NEROX, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist:
Perhaps try again in 15mins?Followed https://discord.com/channels/686873244791210014/1375566093711577118/1375759626620108811 and fixed
who knows why