-
Notifications
You must be signed in to change notification settings - Fork 245
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
Reason to not use package.json
's engines
key?
#355
Comments
Hi @ProLoser, early on we discussed using
We’re also investigating (#282) supporting a separate |
Ah interesting. I also just realized we worked in the same office together lol. You realize this is Dean, right? |
I did :) Figured I’d answer the question first. How are things at PS? And out of curiosity, how did you hear about Notion? |
I don't remember how, but it popped up somewhere during my research. I use fish shell so I've always run into huge problems with |
I actually hadn’t until now, but yeah, exciting! |
The
package.json
has a standardengines
key. Is there a reason for not supporting this in notion vs creating a newtoolchain
key?The text was updated successfully, but these errors were encountered: