fix(schema): prefer mjs in hub schema hook#131
Merged
Conversation
commit: |
This file contains hidden or 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
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.
Summary
schema.<dialect>.mjsoverschema.<dialect>.tsinhub:db:schema:extendresolveHubSchemaPathfor deterministic hook behavior.mjspriority in NuxtHub integration docsWhy
This fixes builds where Nuxt moves
buildDirundernode_modules/.cache/nuxt/.nuxtand Node refuses type-stripping for.tsfiles undernode_modules.Fixes #129
Testing
pnpm vitest run test/schema-hook-path-priority.test.ts✅pnpm testtest/module.test.tsdue existing integration environment issues (port/timeouts and transient module resolution under test output) unrelated to this change