I want to fork React Data Grid repo on Github, make some changes and install it in my react app.
I have added name, version, and description attributes in repo's package.json
I have tried to install it via
npm install username/repo_url#branch
It does install and build the package but is ignoring the dist and lib folder in node_modules/react-data-grid/packages/*/ and I am unable to import it in my code.
I have tried
1) commenting dist in my app's .gitignore
2) adding files attribute with dist in my app's package.json
Nothing works.
What am I doing wrong?
EDIT
Here is the stack trace after following #Derek Nguyen response
npm install piby180/react-data-grid#piby-current
> react-data-grid#1.0.0 postinstall C:\Users\Leo\Documents\Work\demos\myapp\node_modules\react-data-grid
> lerna bootstrap --no-ci && lerna run build
lerna notice cli v3.15.0
lerna info Bootstrapping 2 packages
lerna info Installing external dependencies
lerna info Symlinking packages and binaries
lerna success Bootstrapped 2 packages
lerna notice cli v3.15.0
lerna info Executing command in 2 packages: "npm run build"
lerna ERR! npm run build exited 1 in 'react-data-grid'
lerna ERR! npm run build stdout:
> react-data-grid#7.0.0-alpha.13 build C:\Users\Leo\Documents\Work\demos\myapp\node_modules\react-data-grid\packages\react-data-grid
> tsc
error TS6053: File 'C:/Users/Leo/Documents/Work/demos/myapp/node_modules/react-data-grid/packages/react-data-grid-addons/src/index.ts' not found.
error TS6053: File 'C:/Users/Leo/Documents/Work/demos/myapp/node_modules/react-data-grid/packages/react-data-grid/src/index.ts' not found.
Found 2 errors.
lerna ERR! npm run build stderr:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-data-grid#7.0.0-alpha.13 build: `tsc`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-data-grid#7.0.0-alpha.13 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\Leo\AppData\Roaming\npm-cache\_logs\2019-07-17T14_35_42_219Z-debug.log
lerna ERR! npm run build exited 1 in 'react-data-grid'
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.9 (node_modules\jest-haste-map\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents#1.2.9: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-data-grid#1.0.0 postinstall: `lerna bootstrap --no-ci && lerna run build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-data-grid#1.0.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!
The 'postinstall' script in the package runs lerna bootstrap. According to the doc, it will then do the following:
When run, this command will:
npm install all external dependencies of each package.
Symlink together all Lerna packages that are dependencies of each other.
npm run prepublish in all bootstrapped packages (unless --ignore-prepublish is passed).
npm run prepare in all bootstrapped packages.
The packages in /packages don't have a prepare or prepublish script. You should be able to properly build the subpackage by modifying the root package.json's postinstall script:
postinstall": "lerna bootstrap --no-ci && lerna run build",
I think that should properly build the sub packages.
Related
I want to update the libraries in package.json in a batch, so I executed the command ② after executing the command ①.
After that, I executed the yarn command and the libraries were installed, but when I executed npm install after executing the commands (1) and (2), I got an error.
Why does npm install give me an error?
①rm -rf node_modules yarn.lock
② npx npm-check-updates -u
error
npm ERR! react#"18.2.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"^16.8.0 || ^17.0.0" from #material-ui/core#4.12.4
npm ERR! node_modules/#material-ui/core
npm ERR! #material-ui/core#"^4.12.4" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /user/.npm/eresolve-report.txt for a full report.
you have a dependency conflict in your packages.
#material-ui/core#4.12.4 needs react 16/17 but you are using react 18
upgrade to material-ui v5
OR
use --force flag knowing that there may be some breaking changes
npm install --force
first, I was getting the same error for react-icons. now I am getting errors for the typewriter. it works fine on localhost. when I'm trying to npm i typewriter getting this error:
also tried CI false doesn't worked.
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: cert#0.1.0
npm ERR! Found: react#18.1.0
npm ERR! node_modules/react
npm ERR! react#"^18.0.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.x" from typewriter-effect#2.18.2
npm ERR! node_modules/typewriter-effect
npm ERR! typewriter-effect#"*" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /Users/Dave/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/Dave/.npm/_logs/2022-05-12T15_25_57_631Z-debug-0.log
Cloning completed: 532.695ms
Installing build runtime...
Build runtime installed: 2.177s
Looking up build cache...
Build Cache not found
Installing dependencies...
npm WARN deprecated source-map-resolve#0.6.0: See https://github.com/lydell/source-map-resolve#deprecated
npm WARN deprecated svgo#1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x.
added 1406 packages in 30s
172 packages are looking for funding
run `npm fund` for details
Detected `package-lock.json` generated by npm 7...
Running "npm run build"
> certauto#0.1.0 build
> react-scripts build
Creating an optimized production build...
Failed to compile.
Module not found: Error: Can't resolve 'typewriter-effect' in '/vercel/path0/src/components'
Error: Command "npm run build" exited with 1
it works for me,
go to vercel
Go to your project
settings
install command = npm install --force or npm install --legacy-peer-deps
I am trying to create a project with Vue-Native following the instructions in the documentation:
https://vue-native.io/docs/installation.html
I am trying it with Expo and Vue-React, and in both cases I have the same error when I run "npm start":
Failed to construct transformer: Error: Cannot find module 'vue-native-scripts'
I try to install it with npm install vue-native-scripts --save-dev and I have the error:
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: vuenativetest#0.0.1
npm ERR! Found: react#16.13.1
npm ERR! node_modules/react
npm ERR! react#"16.13.1" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer react#"17.0.1" from react-native#0.64.0
npm ERR! node_modules/react-native
npm ERR! react-native#"^0.64.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/miguel/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/miguel/.npm/_logs/2021-04-04T10_52_07_169Z-debug.log
I updated all libraries: React, React-Native, npm, Node, etc.
But I have the same error.
I am currently working on a vue-native project and encountered this problem when I started.
This seems to be a problem about the dependencies of a vue-native project having sub dependencies of different versions from other dependencies. When NPM sees this it just freaks out.
My solution is to start using yarn! Install it by the following:
$ npm i -g yarn
After its installed, its advised that you delete the project and redo the vue-native-cli init command so it can use yarn from there, but you can also just directly use the following command without deleting the project:
$ yarn install vue-native-scripts
I was trying to create a react project using the command
npx create-react-app chat-app
But I am getting this error.
Creating a new React app in /home/mikhil/react-tutorial/internshala-react-course/chat-app.
Installing packages. This might take a couple of minutes.
Installing react, react-dom, and react-scripts with cra-template...
npm ERR! code ERESOLVE npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! npm ERR! Found: #babel/core#undefined
npm ERR! node_modules/#babel/core npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer #babel/core#"^7.0.0-0" from #babel/preset-env#7.13.10
npm ERR! node_modules/#babel/preset-env
npm ERR! #babel/preset-env#"^7.12.1" from #svgr/webpack#5.5.0
npm ERR! node_modules/#svgr/webpack
npm ERR! #svgr/webpack#"5.5.0" from react-scripts#4.0.3
npm ERR! node_modules/react-scripts
npm ERR! react-scripts#"*" from the root project
npm ERR! npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /home/mikhil/.npm/eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! /home/mikhil/.npm/_logs/2021-03-18T11_58_50_255Z-debug.log
Aborting installation. npm install --save --save-exact --loglevel
error react react-dom react-scripts cra-template has failed.
Deleting generated file... package.json
Deleting chat-app/ from /home/mikhil/react-tutorial/internshala-react-course
Done.
You can try to update npm with npm update and see if that fixes it, and if not you can try these steps.
If you've previously installed create-react-app globally via npm install -g create-react-app, it is recommend you uninstall the package using npm uninstall -g create-react-app or yarn global remove create-react-app to ensure that npx always uses the latest version.
You will also want to delete your remnant files and folders for chat-app
Once you are in the /home/mikhil/react-tutorial/internshala-react-course directory and you have removed the global installations you can try running these commands.
npx create-react-app my-app
cd my-app
npm start
Create React App - Getting Started
I was having the same issue with NPM version 7.20.0.
Simply install an older version of NPM.
In the terminal run: npm install npm#6.14.11 -g
There appears to be some particular versions of NPM that cause this issue. Try updating to the very latest version of NPM.
I was also trying to do the same the whole day, then at last I have to open the documentation, there it was mentioned that you can also create react app using
npm init create-react-app **app_name**
and it worked for me fine.
I was troubled very much by this dependency thing.
I am learning Angular from this tutorial and here is what I have done so far:
I installed Node v0.10.29 successfully on my 64bit Windows 7 machine. After that, while installing yeoman, I got this issue: https://github.com/yeoman/yeoman.io/issues/283
I ignored that issue assuming that its minor and installed generator-angular which was successful. I used cmd as an administrator for all this.
After that, did yo angular and here is what I got:
c:\x-news>yo angular
_-----_
| | .--------------------------.
|--(o)--| | Welcome to Yeoman, |
`---------' | ladies and gentlemen! |
( _'U`_ ) '--------------------------'
/___A___\
| ~ |
__'.___.'__
' ` |° ' Y `
Out of the box I include Bootstrap and some AngularJS recommended modules.
[?] Would you like to use Sass (with Compass)? No
[?] Would you like to include Bootstrap? Yes
[?] Which modules would you like to include?
create app\styles\main.css
create app\index.html
create bower.json
create .bowerrc
create package.json
create Gruntfile.js
invoke angular:common:C:\Users\Rahul\AppData\Roaming\npm\node_modules\gener
ator-angular\app\index.js
create .editorconfig
create .gitattributes
create .jshintrc
create .gitignore
create test\.jshintrc
create app\.buildignore
create app\.htaccess
create app\404.html
create app\favicon.ico
create app\robots.txt
create app\views\main.html
create app\images\yeoman.png
invoke angular:main:C:\Users\Rahul\AppData\Roaming\npm\node_modules\generat
or-angular\app\index.js
create app\scripts\app.js
invoke angular:controller:C:\Users\Rahul\AppData\Roaming\npm\node_modules\g
enerator-angular\app\index.js
create app\scripts\controllers\main.js
create test\spec\controllers\main.js
invoke karma:app
I'm all done. Running bower install & npm install for you to install the require
d dependencies. If this fails, try running the command yourself.
create test\karma.conf.js
create .travis.yml
npm WARN package.json xnews#0.0.0 No description
npm WARN package.json xnews#0.0.0 No repository field.
npm WARN package.json xnews#0.0.0 No README data
npm WARN package.json xnews#0.0.0 No description
npm WARN package.json xnews#0.0.0 No repository field.
npm WARN package.json xnews#0.0.0 No README data
npm WARN deprecated grunt-ngmin#0.0.3: use grunt-ng-annotate instead
npm WARN deprecated ngmin#0.4.1: use ng-annotate instead
bower cached git://github.com/angular/bower-angular-scenario.git#1.2.16
bower validate 1.2.16 against git://github.com/angular/bower-angular-scenar
io.git#1.2.16
bower cached git://github.com/angular/bower-angular.git#1.2.16
bower validate 1.2.16 against git://github.com/angular/bower-angular.git#1.
2.16
bower cached git://github.com/angular/bower-angular-mocks.git#1.2.16
bower validate 1.2.16 against git://github.com/angular/bower-angular-mocks.
git#1.2.16
bower cached git://github.com/es-shims/es5-shim.git#3.1.1
bower validate 3.1.1 against git://github.com/es-shims/es5-shim.git#~3.1.0
bower cached git://github.com/twbs/bootstrap.git#3.2.0
bower validate 3.2.0 against git://github.com/twbs/bootstrap.git#~3.2.0
bower cached git://github.com/bestiejs/json3.git#3.3.2
bower validate 3.3.2 against git://github.com/bestiejs/json3.git#~3.3.1
npm WARN optional dep failed, continuing fsevents#0.2.0
npm ERR! Failed to parse json
ERR! Unexpected string
npm ERR! File: C:\Users\Rahul\AppData\Roaming\npm-cache\send\0.1.4\package\packa
ge.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! cwd c:\x-news
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! file C:\Users\Rahul\AppData\Roaming\npm-cache\send\0.1.4\package\packag
e.json
npm ERR! code EJSONPARSE
npm ERR! Failed to parse json
npm ERR! Unexpected string
npm ERR! File: C:\Users\Rahul\AppData\Roaming\npm-cache\send\0.1.4\package\packa
ge.json
npm ERR! Failed to parse package.json data.
npm ERR! package.json must be actual JSON, not just JavaScript.
npm ERR!
npm ERR! This is not a bug in npm.
npm ERR! Tell the package author to fix their package.json file. JSON.parse
npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nod
ejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "karma-phantomjs-launcher" "k
arma-jasmine" "grunt-karma" "--save-dev"
npm ERR! cwd c:\x-news
npm ERR! node -v v0.10.29
npm ERR! npm -v 1.4.14
npm ERR! file C:\Users\Rahul\AppData\Roaming\npm-cache\send\0.1.4\package\packag
e.json
npm ERR! code EJSONPARSE
--
> phantomjs#1.9.7-15 install c:\x-news\node_modules\karma-phantomjs-launcher\nod
e_modules\phantomjs
> node install.js
Download already available at C:\Users\Rahul\AppData\Local\Temp\phantomjs\phanto
mjs-1.9.7-windows.zip
Extracting zip contents
Copying extracted folder C:\Users\Rahul\AppData\Local\Temp\phantomjs\phantomjs-1
.9.7-windows.zip-extract-1406128242405\phantomjs-1.9.7-windows -> c:\x-news\node
_modules\karma-phantomjs-launcher\node_modules\phantomjs\lib\phantom
Writing location.js file
Done. Phantomjs binary available at c:\x-news\node_modules\karma-phantomjs-launc
her\node_modules\phantomjs\lib\phantom\phantomjs.exe
bower cached git://github.com/jquery/jquery.git#2.1.1
bower validate 2.1.1 against git://github.com/jquery/jquery.git#>= 1.9.0
||
> ws#0.4.31 install c:\x-news\node_modules\karma\node_modules\socket.io\node_mod
ules\socket.io-client\node_modules\ws
> (node-gyp rebuild 2> builderror.log) || (exit 0)
/
c:\x-news\node_modules\karma\node_modules\socket.io\node_modules\socket.io-clien
t\node_modules\ws>node "C:\Program Files\nodejs\node_modules\npm\bin\node-gyp-bi
n\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild
npm WARN optional dep failed, continuing fsevents#0.2.0
bower install json3#3.3.2
bower install es5-shim#3.1.1
bower install angular-scenario#1.2.16
bower install angular-mocks#1.2.16
bower install angular#1.2.16
bower install bootstrap#3.2.0
bower install jquery#2.1.1
\-
json3#3.3.2 bower_components\json3
es5-shim#3.1.1 bower_components\es5-shim
angular-scenario#1.2.16 bower_components\angular-scenario
└── angular#1.2.16
angular-mocks#1.2.16 bower_components\angular-mocks
└── angular#1.2.16
angular#1.2.16 bower_components\angular
bootstrap#3.2.0 bower_components\bootstrap
└── jquery#2.1.1
jquery#2.1.1 bower_components\jquery
-\
> jpegtran-bin#0.2.7 postinstall c:\x-news\node_modules\grunt-contrib-imagemin\n
ode_modules\imagemin\node_modules\imagemin-jpegtran\node_modules\jpegtran-bin
> node index.js
√ pre-build test passed successfully-
> gifsicle#0.1.6 postinstall c:\x-news\node_modules\grunt-contrib-imagemin\node_
modules\imagemin\node_modules\imagemin-gifsicle\node_modules\gifsicle
> node index.js
√ pre-build test passed successfully
> optipng-bin#0.3.9 postinstall c:\x-news\node_modules\grunt-contrib-imagemin\no
de_modules\imagemin\node_modules\imagemin-optipng\node_modules\optipng-bin
> node index.js
√ pre-build test passed successfully
> pngquant-bin#0.3.1 postinstall c:\x-news\node_modules\grunt-contrib-imagemin\n
ode_modules\imagemin\node_modules\imagemin-pngquant\node_modules\pngquant-bin
> node index.js
√ pre-build test passed successfully
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\x-news\npm-debug.log
npm ERR! not ok code 0
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! c:\x-news\npm-debug.log
npm ERR! not ok code 0
app/index.html modified.
c:\x-news>
As you can notice, the first error here is Failed to parse json. Not sure why it is failing.
As per this answer, I did bower install. Nothing was displayed. I assumed it went successful (I checked the version later).
Versions:
c:\x-news>node --version
v0.10.29
c:\x-news>bower --version
1.3.8
c:\x-news>grunt --version
grunt-cli v0.1.13
grunt v0.4.5
c:\x-news>yo --version
1.2.0
c:\x-news>npm --version
1.4.14
I tried this multiple times, starting over, still failed. What am I doing wrong here? Can anyone please point me into the right direction?
Just a tip for anyone running into this issue, the error can be the result of incorrect formatting in your package.json. The terminal error in the question says:
npm ERR! Unexpected string
npm ERR! File: C:\Users\Rahul\AppData\Roaming\npm-cache\send\0.1.4\package\packa
ge.json
So look for something similar in your terminal. It might even point to a specific line number(Note: if it does and you see nothing wrong check a line or two up because the error is often on a line before the one logged in the console error). In my case it pointed to a trailing ',' that caused the JSON parse error.
Carefully go through the package.json line by line. If you don't find anything that could be causing the problem then run npm cache clean and npm install again as suggested above. Hope that helps someone!