Skip to content

Conversation

@danielroe
Copy link
Contributor

resolves #166
closes #167

@farnabaz
Copy link
Collaborator

Do you think we should use this pattern in all modules? Because other modules will face the same issue with module builder,
Like image module https://github.com/nuxt/image/blob/e7242fbc2bb37d484f1c903e8a28532973b11ddb/src/runtime/utils/meta.ts#L1-L3

@danielroe
Copy link
Contributor Author

Indeed, we should.

@atinux atinux merged commit 4ff9609 into main Jun 14, 2024
@danielroe danielroe deleted the fix/runtime-type-imports branch June 14, 2024 09:37
@danielroe
Copy link
Contributor Author

@farnabaz Nice spot. That is actually already broken, even with v0.6.0 of the module builder.

@pkg-pr-new
Copy link

pkg-pr-new bot commented Jul 17, 2025

npm i https://pkg.pr.new/@nuxthub/core@168

commit: 5f71b74

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The type inferences for hubDatabase and hubKV methods are gone

4 participants