You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
process.env results in an OS call for every access, and can be very slow if called on every request to check environment for some reason. Typical usage should recommend that process.env be only used in the configs (i.e. in the filers under config/) but there could be scenarios where a user may want to access it directly.
Caching it would also allow the system to throw an error if the user (or malicious code) attempts to modify process.env during runtime.
Issue Description
process.env
results in an OS call for every access, and can be very slow if called on every request to check environment for some reason. Typical usage should recommend thatprocess.env
be only used in the configs (i.e. in the filers underconfig/
) but there could be scenarios where a user may want to access it directly.Caching it would also allow the system to throw an error if the user (or malicious code) attempts to modify
process.env
during runtime.See:
tmpdir
be const value nodejs/node#1648 (comment)Environment
The text was updated successfully, but these errors were encountered: