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

Worth using NODE_COMPILE_CACHE when detecting node v22+ #1845

Open
kurtextrem opened this issue May 2, 2024 · 3 comments
Open

Worth using NODE_COMPILE_CACHE when detecting node v22+ #1845

kurtextrem opened this issue May 2, 2024 · 3 comments
Labels
feature-request Request for new features or functionality
Milestone

Comments

@kurtextrem
Copy link

kurtextrem commented May 2, 2024

see: nodejs/node@4d77fd2

might be worth using? (maybe as a setting)

for people interested, this might work for TS today:

"typescript.tsserver.nodePath": "NODE_COMPILE_CACHE=node_modules node",

but eslint's nodePath is different, so I think this might need a patch or so.

@dbaeumer dbaeumer added the feature-request Request for new features or functionality label May 6, 2024
@dbaeumer dbaeumer added this to the Backlog milestone May 6, 2024
@dbaeumer
Copy link
Member

dbaeumer commented May 6, 2024

ESLint supports a eslint.execArgv setting. You could add this right now, but no auto detection.

@kurtextrem
Copy link
Author

I might be missing something, but I think the node compile cache is only available as env var, so setting execArgv would not help?

@dbaeumer
Copy link
Member

dbaeumer commented May 7, 2024

You are correct. I missed that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

2 participants