-
-
Notifications
You must be signed in to change notification settings - Fork 58
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
feat: updated to turbo v2 #72
Conversation
|
"typescript": "^5.4.5", | ||
"yargs": "^17.7.2" | ||
} | ||
}, | ||
"packageManager": "[email protected]" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
does this actually work?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ohhh makes sense then.
bun turbo lint barked as it preferred dot notation instead of square brackets
@@ -27,7 +27,7 @@ export const env = createEnv({ | |||
}, | |||
client: {}, | |||
experimental__runtimeEnv: { | |||
NODE_ENV: process.env['NODE_ENV'], | |||
NODE_ENV: process.env.NODE_ENV, | |||
}, | |||
emptyStringAsUndefined: true, | |||
skipValidation: !!process.env['SKIP_ENV_VALIDATION'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Curious why eslint doesn't have a problem with ['SKIP_ENV_VALIDATION']
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
because NODE_ENV
is known to be on process.env
but SKIP_ENV_VALIDATION
isn't
No description provided.