i am building an app that uses react-router,flux and i found this library called redux-auth(https://github.com/lynndylanhurley/redux-auth). I am trying to use it since it has a lot of work done regarding loging,sign up, etc.
I installed the dependencies with npm in this order - >
npm install redux-auth --save
npm install material-ui --save
npm install react-tap-event-plugin
After this i got the error i mention, the module isActive cannot be found.
So i searched the web and found this post:
https://github.com/acdlite/redux-router/issues/111
Where they fix it with this command: npm install --save history react-router#latest followed by npm install --save redux-router#1.0.0-beta3
After this my app broke, and now i get the error : "Error: ajax not supported in this browser" when prerendering Router with / and {}
The line with such error: <%= react_router 'Router', 'HistoryLocation', {}, { prerender: params[:noprerender].nil?, prerender_location: root_path } %>
Tried uninstalling such libraries but didn't work out, tried removing the node_modules dir and rebuilding with npm but didn't work.
Any help or advice? is impossible for me to use this library? is it maybe a compability problem between flux and redux? Any help is welcome.
Edit #1 : I am using Chrome.
Related
Uncaught SyntaxError: Private field '#map' must be declared in an enclosing class
Suspect that npm is broken for openlayers (or openlayers is broken for npm)... it worked this morning until I did an npm update and now its all broken and stupid...
I had upgraded to npm 7.19.1 which npm cheerfully chirped about - I downgraded back to the npm 6.14.13 that comes with FC33. I'm also still learning to avoid installing npm modules with "sudo"...
Upgrading to 7.x npm start/build demanded that be used - and once you use it the .css in the example index.html from openlayers examlpes gets broken right at "#map" or ".map"...
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.
I am trying to set up for the react native. but whenever I update files it gives m error
enoent ENOENT: no such file or directory, open 'React Native/package.json'
npm WARN react-native#0.26.3 requires a peer of react#15.0.2 but none was installed.
npm WARN React Native No description
npm WARN React Native No repository field.
npm WARN React Native No README data
npm WARN React Native No license field.
MacBook-Pro:React Native$ npm info react dist-tags.latest
Please let me know how can I fix.
Installing react should fix the error
npm install react --save
Also, you may try upgrading your react-native install. react-native is as v0.30.0 now
npm update react-native
In my specific case I was running npm install in the wrong directory. I thought I was in my project directory but was one level higher. This meant react was missing from installed packages (because there were none) and thus gave this error.
Some steps that worked for me:
1. watchman watch-del-all
2. rm -rf node_modules
3. npm install react#15.0.2 --save
4. npm install react#15.1.0 --save
5. npm install
6. rm -fr $TMPDIR/react-*
7. npm start -- --reset-cache
In my case, the project I am working on requires a specific version of React. Since it was older than the current release, doing an install/update would still cause the error.
In order to fix the problem, I had to check the package.json of the project and install the exact version allowed by the dependency definition. In the OP's case, a
npm install react#15.0.2
should fix the problem by installing the exact version of the React module that react-native requires.
Verify that the condition was resolved by doing a npm list to see if there are any other unmet peer dependencies.
I typed sudo npm install -g bower getting this issue again and again
/usr/local/bin/bower -> /usr/local/lib/node_modules/bower/bin/bower
bower#1.7.2 /usr/local/lib/node_modules/bower
└── semver-utils#1.1.1
This doesn't look like an error at all. semver-utils is a library required by bower after 1.7.1.
Maybe run bower in the command line and show us the error you're getting.
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.