Luke Karrys comments

Results 170 comments of


                                            Luke Karrys

npm which function fails to get full path to an executable in macOS within an Electron app running in production mode but, works fine in development mode

This issue looks to be solved by the previous comment. If that's not the case, please reopen or file a new issue.

[BUG] SemVer.compare causes spurious allocations of SemVer objects

using this issue as a reference for auditing the creation of all `new Semver/Range` classes when called from methods. `semver` tries to reuse instances in some cases but not others....

[QUESTION] includePrerelease usage

I think this question has been answered. If not, please reopen or open a new issue.

[FEATURE] add methods to update a range, including operator

One area this would be useful is when getting a range and attempting to increase the range somehow. Maybe there is less use of an `.operator()` method if that existed?...

[FEATURE] add methods to update a range, including operator

Updated the title of the issue to increase its scope.

cannot install

This looks like an issue with `npm` itself. If you are still having problems you can open a new issue at https://github.com/npm/cli/issues/new/choose

[FEATURE] command -v is preferable (usually) to which

> Correct me if I'm wrong, but this package does not use which. Rather it just imitates its functionality. This is correct. This package does not invoke any commands, but...

[BUG] npm produces "timing" log output when "npm start"

> What is the fix version for this bug? @synox this was fixed in `9.0.0`. technically it was fixed in one of the v9 prereleases, but 9.0.0 is the first...

SSR mismatch errors

This is due to a Gatsby bug: https://github.com/gatsbyjs/gatsby/issues/36956. This is only an error in dev_sat mode and not in production according to the issue.

feature idea: ship non-default shell bindings for getting one command at a time

Linking to a previous discussion I found about this: https://github.com/ellie/atuin/discussions/543. Seems like others using `NOBIND` and the builtin shell history for `^up`. This is far easier than my proposed solution,...