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.

Sign up for GitHub

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

Jump to bottom

Node engine #662

Closed
rchl opened this issue Aug 1, 2022 · 1 comment · May be fixed by WontonSam/Cachimanstarter.dev#384
Closed

Node engine #662

rchl opened this issue Aug 1, 2022 · 1 comment · May be fixed by WontonSam/Cachimanstarter.dev#384

Comments

@rchl
Copy link
Member

rchl commented Aug 1, 2022 •
edited
Loading

Was just wondering whether forcing latest minor/patch node version in:

composition-api/package.json

Line 113 in 7c6bb1c

"node": ">=v14.20.0"

is a good idea in general.

If the older 14.* version has no obvious compatibility issues then limiting it to the latest seems unnecessary and problematic as it forces users of the package to use the latest node.
@danielroe
Copy link
Member

You are right. This should be >=14.13.0 for subpath import support.

@WontonSam WontonSam mentioned this issue Sep 15, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@rchl @danielroe