Skip to content
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

Open
silverbackdan opened this issue Jun 18, 2020 · 2 comments
Open

Need to resolve dependencies when built #13

silverbackdan opened this issue Jun 18, 2020 · 2 comments
Labels
Nuxt 2 Module (Outdated) wontfix This will not be worked on

Comments

@silverbackdan
Copy link
Contributor

For dev the typescript works well to link @cwa/nuxt-module to the src. Because we will be releasing the packages under 2 different names nuxt-module and nuxt-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.

@silverbackdan
Copy link
Contributor Author

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.

@silverbackdan
Copy link
Contributor Author

silverbackdan commented Sep 1, 2020

NPM package now @cwa/nuxt-module and @cwa/nuxt-module-next as we were able to obtain the cwa organisation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Nuxt 2 Module (Outdated) wontfix This will not be worked on
Projects
None yet
Development

No branches or pull requests

1 participant