Conflict with built-in command? about preset HOT 5 CLOSED

Note: after reading the docs, I found you can use --ignore-existing to deny npx from looking into $PATH.

from preset.

I experience this problem and never mentioned it because I thought it was just a problem with my own setup. Do npm install --save-dev apply before running npx apply ... as a workaround. (Then uninstall it later.)

from preset.

Hey, yeah, this issue has been reported to me before. This is quite annoying, I'm not exactly sure what's the best way to handle it.

There are a few workarounds:

• As @babichjacob said, install apply locally so npx can use it
• Use use-preset instead of apply, which is an alias on NPM that I maintain

I should probably document that for macOS users.

from preset.

Hi,

Just tried use-preset but it doesn't work.

I end up using @babichjacob's solution. Kudos.

@innocenzi :

Too bad since I think this is a very useful project.

According to this page:

The apply command appeared in 4.2BSD.

The shown date is April 4, 1994. So two things for sure:

• This is not a macOS specific issue.
• The command has been around for a very long time.

from preset.

Ah, well, that's unexpected. But after thinking about it, I'd rather advice installing apply locally than confusing people about the use-preset alias, anyway. Not exactly sure why it doesn't work though.

This is not a macOS specific issue.

From my understanding, macOS has parts of FBSD and that's where the issue comes from. So any OS based on FBSD will have this problem. Thanks for pinning down the issue, I'll update the docs. 👍

from preset.