Merged
Conversation
Member
Author
|
Hey @antfu, I tried something out here: using an extra CI forced to NodeJS v14.6
It looks like as we are using pnpm (same as in Vite) we are forced to at least that version 🤔
|
Shinigami92
force-pushed
the
use-node-import-prefix
branch
from
0abf4a7 to
7d416d8
Compare
Member
Author
|
I can use |
Shinigami92
force-pushed
the
use-node-import-prefix
branch
2 times, most recently
from
cbf9d2f to
85f6b47
Compare
Shinigami92
force-pushed
the
use-node-import-prefix
branch
from
85f6b47 to
48457b1
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No description provided.