fix: ssr require module failing with "Cannot find module './emojis'" #1784
+1,376
−2,291
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- update package.json:
- dependencies:
- nuxt ^3.15.3 -> ^3.15.4
- @iconify-json/octicon ^1.2.2 -> ^1.2.4
- @iconify-json/simple-icon ^1.2.22 -> ^1.2.24
- devDependencies:
- @nuxt/eslint ^1.0.0 -> ^1.0.1
- eslint ^9.19.0 -> ^9.20.0
- shiki ^2.1.0 -> ^2.3.2
- vitest ^3.0.4 -> ^3.0.5
- re-build pnpm-lock.yaml
closes nuxt#1783
mhoffrog
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
#1783
❓ Type of change
📚 Description
This kind of issue was determined with Nuxt v3.15.3 only see nuxt-modules/MDC issue#318 for reference.
It has been fixed in Nuxt v3.15.4 by Nuxt PR fix(vite): restore externality for dev server externals #30802.
So this issue can be fixed by upgrading dependencies
update package.json:
re-build pnpm-lock.yaml
Known Issue
Nuxt
3.15.4is coming with a dependency update of@nuxt/clito3.21.1. This update fixes thetypecheckcommand to let the node process end with an exit code <>0 if there are typecheck errors found. This is currently breaking this projects GitHub Actionci.xml. Fixing this projects typecheck violations should be subject of another PR.See @nuxt/cli fix: throw when errors are #encountered
Test Results
No error is thrown anymore:
Page is rendering as expected:
