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
In the check method we pass the options object as a command line argument to check.js (see relevant line here). This means we pass the entire content of package.json as a command line argument (at least if the user followed the examples and didn't pass a custom pkg object). This is a potential problem, since certain platforms have a limit to the maximum length of the command line string (at least Windows does). So it can cause issues with really big package.json files. I think it would be better, if we update options.pkg (in the UpdateNotifier constructor) to contain just the relevant keys (name and version), so this will never become an issue.
The text was updated successfully, but these errors were encountered:
We rewrite `options.pkg` to hold only the information we need (name and
version). So when we call node with check.js we no longer pass the
entire content of package.json as a command line argument.
This resolvessindresorhus#57.
In the
check
method we pass the options object as a command line argument to check.js (see relevant line here). This means we pass the entire content of package.json as a command line argument (at least if the user followed the examples and didn't pass a custompkg
object). This is a potential problem, since certain platforms have a limit to the maximum length of the command line string (at least Windows does). So it can cause issues with really big package.json files. I think it would be better, if we updateoptions.pkg
(in theUpdateNotifier
constructor) to contain just the relevant keys (name and version), so this will never become an issue.The text was updated successfully, but these errors were encountered: