-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Need to resolve dependencies when built #13
Labels
Comments
The components web app currently uses aliases to resolve and is working. We may need to do that for using current or next versions as well. Currently using this method because the npm package name is not set in stone. |
NPM package now @cwa/nuxt-module and @cwa/nuxt-module-next as we were able to obtain the cwa organisation. |
silverbackdan
added
wontfix
This will not be worked on
Nuxt 2 Module (Outdated)
and removed
Hacktoberfest
labels
Jun 19, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For dev the typescript works well to link
@cwa/nuxt-module
to thesrc
. Because we will be releasing the packages under 2 different namesnuxt-module
andnuxt-module-next
we need to work out how we can dynamically import from either one from within the built application.The user will manually specify which one as they know which package they have installed, it's only for the internal references we need to worry about this.
The text was updated successfully, but these errors were encountered: