Yeoman : no generator installed error - yeoman

I'm trying to setup angularfire generator.
I did npm install -g generator angularfire
The generator was installed successfuly.
And when I run yo angularfire in my newly created directory,it asks few options like firebase instance and which modules to include , but after that it shows the following error
You don't seem to have a generator with the name angularfire:common:C:\Users\SATWIK\AppData\Roaming\npm\node_modules\generator-angularfire\app\index.js installed.
Also I've checked that the file index.js does exist at this path.
As suggested in some of the answers on stackoverflow I've also tries npm install -G generator-angularfire and npm install generator-angularfire but none of them worked.
I also did yo doctor but it shows Everything is fine . Is there any fix to this problem?

This is a regression we had in our last release. It's now fixed https://github.com/yeoman/environment/releases/tag/v1.5.2
npm -g update yo to fix that issue.

Related

vips/vips8 file not found #include <vips/vips8> in Ionic cordova in IOS

I found an error in sharp.
After that, I found a blog in which they ask to delete sharp from the node module and run sudo npm i.
I have gone through GitHub and write minipass - 2.7.0
After that, I got a new error in
vips/vips8 file not found #include <vips/vips8>
I'm using Ionic with Angular on Macbook
I use commands which is
1.sudo npm install
2.sudo npm i gulp-sass -ES --unsafe-perm=true
3.sudo ionic cordova platform add ios
I very recently ran into a similar issue after making some changes to a project's package.json on my Mac (not an Angular or Cordova project).
I came across this GitHub issue for the sharp package which mentioned you may need to update the globally-installed version of libvips: https://github.com/lovell/sharp/issues/1148
In my case, since I use Homebrew but had not directly installed this package previously, I was able to resolve by running brew install vips and then re-running npm install. Note that it has a lot of dependencies so installation may take some time.
Edit: if that doesn't work, you may need to try a fresh install by removing node_modules, then re-running npm i.
This might be not applicable to everyone, but remove package-lock.json and node_modules directory first and then try npm install again. (I also added the minipass in my package.json, by the way)
In my case, I had encountered the same error, but I could solve it by doing the above.

Command `bundle` unrecognized. Did you mean to run this inside a react-native project?

I am currently upgrading to the most recent version of react from 0.11.0 branch.
I have upgraded successfully through each step with minimal issues but when I got to 0.14.0 I hit some issues with:
node_modules/react-native/packager/react-native-xcode.sh
No matter what I do all my machines seem to get this same error.
Command `bundle` unrecognized. Did you mean to run this inside a react-native project?
I also run this same command that script runs from my terminal in the same location and it works fine, I have also set the path as well and before the script runs no mas, set path inside the script still nothing.
I am hoping someone else has saw this and has found a solution or is there a work around so we dont need this script.
I started this project with react-native ~0.6.0 maybe even a little earlier.
I have even removed nvm to combat this issue and using single install of node which is on PATH in both conditions.
Thanks!
Have you installed the latest version of react-native-cli globally?
npm uninstall -g react-native-cli
npm install -g react-native-cli
I personally preferred to install it as a dev dependency.
yarn add -D react-native-cli

yo aspnet generator not detected

I am using ubuntu vivid. Trying to use yeoman aspnet generator. Installed the generators using below commands
sudo npm install -g yo
sudo npm install -g generator-aspnet
When i try using it using the command : yo aspnet
i get the below error
Error aspnet
You don't seem to have a generator with the name aspnet installed. You can see available generators with npm search yeoman-generator and then >install them with npm install [name]. To see the 0 registered generators run yo with the `--help` option.
I am able to see the generator files under /usr/local/lib/node_modules/generator-aspnet
What am i missing?
For any Yeoman issues, always run yo doctor.

ionic build ios fails with "[TypeError: Arguments to path.join must be strings]"

I am trying to create an ionic app on Mac.
I followed the instructions on ionic's website to create a basic app and was able to run it in the browser but when I run "ionic build ios" I get following error. I cannot find a log file or any other error to debug this. How do I go about fixing this?
Check your Gulp version and gulpfile.js. You may need to remove the calls to gulp.src
See:
Gulp TypeError: Arguments to path.join must be strings
and
https://github.com/sindresorhus/gulp-ruby-sass/issues/191
ok, after lot of looking and searching I figured my npm install was messed up.
Part of my installs were in /usr/local and few of them were in /User/user.name/npm folders. /Users/user.name/npm was set in the npm config prefix.
I had two installs of cordova, one on each folder above. Some how the cordova from /usr/local was getting used to create the project and that was the old version.
To fix the problem, I uninstalled all my global npm installs and pointed my npm config prefix to /usr/local and gave myself execute permission on that folder. Everything is working now.
Here is the video that explains how to do it: https://docs.npmjs.com/getting-started/fixing-npm-permissions

Yeoman generator update

I'm getting this error when I'm trying to update my custom generator.
npm ERR! 404 'generator-blsp' is not in the npm registry.
The generator is working just fine, the old version.
I did some minor changes in the generator and changed the version number.
Then I ran the update generator function from the yo menu, I can still see the symlink to my project in /usr/local/lib/node_modules/
Have I missed a step or something?
Apparently I had 2 installations of node with the old generator installed in the other installation.
/usr/lib/node_modules
&&
/usr/local/lib/node_modules/

Resources