I'm trying to follow the wikipedia ios project at https://github.com/wikimedia/apps-ios-wikipedia/ and I'm having problem while running "make get-deps". I always got the prompt of "Missing node v0.10 and/or higher and npm 1.4 or higher", but I do have the node & npm installed already.
The version of node is v0.12.0 and the version of npm is 2.5.1.
Relevant code is here. The Makefile is essentially asking for npm#1.4; the message says "1.4 or higher" but really the code is only checking for 1.4 (despite npm#2's existence for a few months now). Until they update that, you might be able to simply comment out the exit 1 so that the process continues.
Related
When I try to install serverless framework I get the following deprecations. I've run an npm install on each individual package. Npm says the package installs worked, but it doesn't change the sls output. I reinstalled Windows thinking I may have changed a config file at some point, still the exact some output even after reinstall. I'm running Windows 10. I am stuck and any help would be appreciated.
C:\Users\User>npm install -g serverless
npm WARN deprecated querystring#0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated formidable#1.2.6: Please upgrade to latest, formidable#v2 or formidable#v3! Check these notes
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated querystring#0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid#3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated superagent#3.8.3: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at https://github.com/visionmedia/superagent/releases.
these deprecations are related to the libraries version that are used directly by serverless. You can expect them to sooner or later be addressed on that library level but until that, you can use it without worries (unless you see the explicit security warnings, but that's not the case at the moment).
I wanted to start practicing with React to make a simple app. Went ahead and downloaded homebrew and node onto my computer. As I build my app with yarn install I get to the end where it tells you happy hacking. But when I run yarn start it gives me an error message.
-There might be a problem with the project dependency tree.
It is likely not a bug in Create React App, but something you need to fix locally.
The react-scripts package provided by Create React App requires a dependency:
"eslint": "^6.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of eslint was detected higher up in the tree:
/Users/zacharyschneider/node_modules/eslint (version: 5.16.0)
Manually installing incompatible versions is known to cause hard-to-debug issues.
If you would prefer to ignore this check, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That will permanently disable this message but you might encounter other issues.
To fix the dependency tree, try following the steps below in the exact order:
1. Delete package-lock.json (not package.json!) and/or yarn.lock in your project folder.
2. Delete node_modules in your project folder.
3. Remove "eslint" from dependencies and/or devDependencies in the package.json file in your project folder.
4. Run npm install or yarn, depending on the package manager you use.
In most cases, this should be enough to fix the problem.
If this has not helped, there are a few other things you can try:
5. If you used npm, install yarn (http://yarnpkg.com/) and repeat the above steps with it instead.
This may help because npm has known issues with package hoisting which may get resolved in future versions.
6. Check if /Users/zacharyschneider/node_modules/eslint is outside your project directory.
For example, you might have accidentally installed something in your home folder.
7. Try running npm ls eslint in your project folder.
This will tell you which other package (apart from the expected react-scripts) installed eslint.
If nothing else helps, add SKIP_PREFLIGHT_CHECK=true to an .env file in your project.
That would permanently disable this preflight check in case you want to proceed anyway.
P.S. We know this message is long but please read the steps above :-) We hope you find them helpful!
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
zacharyschneider#Zacharys-MBP %
A way to solve this issue or help me understand what is going on that would be great or point me in the right direction to find resources.
Thanks for your Help
It seems like you have installed es-lint 5.16.0 manually, and it conflicts with the needed version (6.6.0).
Have you tried the steps suggested in the error message?
Do you explicitly tell the es-lint version in your package.json? Could you share your package.json if you continue to experience the issue?
I cd to my react-native project directory, and run flow, it prompts me Launching Flow server for /Users/... Wrong version of Flow. The config specifies version ^0.32.0 but this is version 0.33.0. How do I install the previous version flow with Homebrew?
If you run brew info flow in the console, you'll see a line similar to the following:
flow: stable 0.33.0 (bottled), HEAD
This means that the person managing the flow homebrew formula is removing old versions as the version gets updated, so it's impossible for you to access any old versions, barring performing some behind the scenes business I'm unaware of.
Luckily, there's a solution for you. I assume you're using npm, in which case you can try the following:
npm install flow-bin#0.32 -g
This will install a binary wrapper for flow, packaged through npm, in which previous versions are all available. By installing globally, you can use the flow commands in the command line.
If you don't want to install globally, for fear of conflicting with other projects, etc., you can still install locally and use flow:
npm install flow-bin#0.32
Now, add the following to package.json:
"scripts": {
...
"flow": "flow ."
},
And now, you'll be able to run flow on your project with the command:
npm run flow
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
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/