Jason Marshall
Jason Marshall
I think we have already hit the point where an advice section in the README would be good to mention that while there are 20 different filenames node-config could load...
The question I think Loren leaves open is "where do you slot platform into the normal precedence". > {short_hostname}.EXT {short_hostname}-{instance}.EXT {short_hostname}-{deployment}.EXT {short_hostname}-{deployment}-{instance}.EXT {full_hostname}.EXT {full_hostname}-{instance}.EXT {full_hostname}-{deployment}.EXT {full_hostname}-{deployment}-{instance}.EXT I feel like these...
> TypesScript. For https://github.com/evanw/esbuild/issues/257 and other deep type reflection features. Is that a bad thing in a config library? Least Power suggests to me that reflection in load time logic...
> Do you know if this plays nice with nyc? Sadly, no. `SyntaxError: Missing initializer in const declaration`
I was hoping for advice from the Istanbul people but no luck so far https://github.com/istanbuljs/nyc/issues/1595
Depending on how this ticket plays out, we may need to overlook the downsides of this solution. @lorenwest @markstos https://github.com/nodejs/node/issues/59364
> swarm or Kubernetes In fact for us it's worse than this. We run a collector on a common host image, so it's every docker container we deploy, not just...
I looked at the code for the slab metadata before filing the issue. It is... not well-contained. It's going to take someone with experience in this code base to do...
What about glob?