fix: change type to avoid name conflict #57
Closed
Conversation
This file contains 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
|
could you rename the type when importing? something like: |
|
Do you mean in nuxt-script ? No because due to the name conflict, the type isn't exported in the build result |
ah got it - that makes sense... I'll adjust |
|
@flashdesignory google_tag_manager doesn't need to be removed from types i think |
|
closing, since this has been addressed with #54 |
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.
Hey 👋
this PR fix the ci of nuxt/scripts#176 . This is caused by a type GoogleTagManager and a var GoogleTagManager so it conflicts at build time. This PR renmae the type to GoogleTagManagerIsntance