π Description
After upgrading from @nuxthub/core@0.10.4 to 0.10.5, imports inside
server/db/schema stopped working when using the #shared Nuxt alias.
β
What worked before (0.10.4)
Imports like the following worked correctly:
import { something } from '#shared/utils/accounts'
β What happens in 0.10.5
At runtime, Node throws the following error:
Package import specifier "#shared/utils/accounts" is not defined in package
.../node_modules/@nuxthub/db/package.json
π Observation
This appears to be a behavior change compared to 0.10.4.
Schema imports now rely on Node-only module resolution.
π‘ Expected behavior / suggestion
Either:
-
π Document clearly that server/db/schema must not rely on the #shared
alias and should use Node-resolvable imports, or
-
π§ Preserve #shared alias resolution for schema imports if possible.
Happy to adjust code β just wanted to report this since it wasnβt obvious
during the upgrade π
π Description
After upgrading from
@nuxthub/core@0.10.4to0.10.5, imports insideserver/db/schemastopped working when using the#sharedNuxt alias.β What worked before (0.10.4)
Imports like the following worked correctly:
β What happens in 0.10.5
At runtime, Node throws the following error:
Package import specifier "#shared/utils/accounts" is not defined in package
.../node_modules/@nuxthub/db/package.json
π Observation
This appears to be a behavior change compared to 0.10.4.
Schema imports now rely on Node-only module resolution.
π‘ Expected behavior / suggestion
Either:
π Document clearly that server/db/schema must not rely on the #shared
alias and should use Node-resolvable imports, or
π§ Preserve #shared alias resolution for schema imports if possible.
Happy to adjust code β just wanted to report this since it wasnβt obvious
during the upgrade π