Need to have configuration files for each NODE_ENV variable

cherfia / chromiumly

A lightweight Typescript library that interacts with Gotenberg's different modules to convert a variety of document formats to PDF files.

MIT License

54 stars 7 forks source link

Need to have configuration files for each NODE_ENV variable #411

Open forg002-ctrl opened 4 days ago

forg002-ctrl commented 4 days ago

I get this error every time I start my project: │ WARNING: NODE_ENV value of 'staging' did not match any deployment config file names.
│ WARNING: See https://github.com/node-config/node-config/wiki/Strict-Mode

cherfia commented 4 days ago

@forg002-ctrl Thanks for reporting this. It is not an error but just a warning. I'll update chromiumly to suppress this warning message. 👍

cherfia commented 3 days ago

@forg002-ctrl I noticed that the warning occurs when you install chromiumly along with its optional dependencies (i.e., without using the --omit=optional flag). This would include the config package, which enforces Strict Mode, requiring the presence of a config file related to the Node environment. 👀

Anyway, the newest version 3.5.0 should solve this issue. Could you please try it out and let me know if it resolves it for you?