| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
🤔 no code-owners... wonder who I should ping, or create a team |
Sorry, something went wrong.
Codecov ReportAttention: Patch coverage is 96.66667% with 2 lines in your changes missing coverage. Please review.
@@ Coverage Diff @@
## main #57170 +/- ##
=======================================
Coverage 90.35% 90.35%
=======================================
Files 629 629
Lines 184308 184394 +86
Branches 36015 36027 +12
=======================================
+ Hits 166532 166617 +85
+ Misses 10909 10902 -7
- Partials 6867 6875 +8
... and 25 files with indirect coverage changes 🚀 New features to boost your workflow:
|
Sorry, something went wrong.
There was a problem hiding this comment.
I would rather not use the namespace and just specify a specific file that we use instead of letting the user define the filename.
Sorry, something went wrong.
I added the default file in #57171, about namespacing I think its a necessary evil, otherwise we will regret it if the feature grows |
Sorry, something went wrong.
I think we need a @nodejs/cli team or something, to cover this feature and --env-file. Please add me if you create one. |
Sorry, something went wrong.
There was a problem hiding this comment.
There was discussion in old issues about supporting various environments, like top-level fields such as dev or localhost or prod etc. I don't have an opinion as to how multiple environments or multiple config files should be handled, but I feel like this is something to be worked out now as we're discussing namespacing. If the answer is that we're just not going to provide any explicit support for merging config files or supporting multiple environments within one config file, that's fine, but I think we should have that discussion.
Sorry, something went wrong.
There was a problem hiding this comment.
Can we support all of experimental-transform-types, experimental_transform_types and experimentalTransformTypes for each flag? Just as currently the CLI supports either of the first two.
Sorry, something went wrong.
There was a problem hiding this comment.
I'm ok with the second, not sure how feasible is the third one. I think we can defer to a followup
Sorry, something went wrong.
There was a problem hiding this comment.
Given this is just a sample of how to use the config file to persist flags, would it be better to stick to non-experimental flags?
This example maximizes hiding of the dependency on experimental features, e.g. by disabling the warnings too. That's fine if you are experienced enough to understand the implications.
Whilst it's certainly possible to use configs for this purpose, having it as the shining model example seems risky IMO and may be construed as encouragement to use this pattern.
Sorry, something went wrong.
There was a problem hiding this comment.
will do in the followup PR #57171 since this is ready to land and we have added the not-land-on-v23
Sorry, something went wrong.
|
I dont think we should support different environments in the same file, users can use the dev.config.json and the prod.config.json |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #57170 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
PR-URL: #57170 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
PR-URL: #57170 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
PR-URL: #57170 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
PR-URL: nodejs#57170 Backport-PR-URL: nodejs#57958 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
PR-URL: nodejs#57170 Backport-PR-URL: nodejs#57958 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Paolo Insogna <paolo@cowtech.it>
| Back | FazBrowse Home | New Git URL |
follow-up: #57016 (comment)