-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Beefy does not find bundlers when there's an alternate npm global install path #70
Comments
I can look for a fix maybe this weekend or sometime but don't wait up for me ⌚ 👀 |
This is also affecting me, apparently. |
I trued sym-linking my brew npm into /usr/bin... that didn't help. however |
had same problem, npm install -g browserify worked for me too |
Also seeing this issue. I have For the record, Beefy might be able to utilize this: |
With this command
I am seeing
even though browserify is global and the command |
I can't get beefy to find browserify no matter what I can think of to try. Can someone show me a setup that works?
|
If you can't get it to work @mark-hahn you may have better luck with one of these tools: https://github.com/mattdesl/budo |
Thanks. It's nice to know about these three options. I got beefy to work by moving both beefy and browserify to local node_modules and removing the global installs. I also switched to just running a node file in my root directory with the beefy server code. |
I had same problem, solved it by adding --browserify $(which browserify) to the beefy start script in package.json of my project. |
@ajuc This works for me. Because I'm using zsh, so I add |
I install global packages in
~/npm/
.npm
exists in/usr/bin
. Beefy seems to rely on the location ofnpm
when looking for bundlers rather than callingwhich
on the actual executable (e.g.watchify
).When I add
console.log(dir[i])
in the for loop insetup-bundlers.onglobals
I see that it's not looking in my~/npm/
directory for browserify/watchify:The text was updated successfully, but these errors were encountered: