I made a project (on macos) with "create react app" and committed on git.
Now I'm cloning the folder on Windows and I'm following usual steps:
node
npm
npm install
Anyway I'm having this issue back:
$ npm start
> name#0.1.0 start \\Mac\Home\Desktop\WindowsProgetti\WebApp
> react-scripts start
'\\Mac\Home\Desktop\WindowsProgetti\WebApp'
CMD.EXE è stato avviato utilizzando il percorso precedente come directory
corrente. I percorsi UNC non sono supportati. Per impostazione predefinita,
verrà utilizzata la directory di Windows.
internal/modules/cjs/loader.js:583
throw err;
^
Error: Cannot find module '\\Mac\Home\Desktop\WindowsProgetti\WebApp\node_modules\react-scripts\bin\react-scripts.js'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
at Function.Module._load (internal/modules/cjs/loader.js:507:25)
at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
at startup (internal/bootstrap/node.js:279:19)
at bootstrapNodeJSCore (internal/bootstrap/node.js:752:3)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! name#0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the matchplat#0.1.0 start 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\fabio\AppData\Roaming\npm-cache\_logs\2018-09-21T13_56_21_061Z-debug.log
(I know... something is in Italian language, most important stuff is English anyway.)
Package.json
{
"name": "name",
"version": "0.1.0",
"private": true,
"homepage": "http://localhost:3000",
"dependencies": {
"#material-ui/core": "^3.0.0",
"#material-ui/icons": "^3.0.0",
"create-react-app": "^1.5.2",
"react": "^16.4.2",
"react-dom": "^16.4.2",
"react-intl": "^2.4.0",
"react-loadable": "^5.5.0",
"react-router-dom": "^4.3.1",
"react-scripts": "1.1.5"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test --env=jsdom",
"eject": "react-scripts eject"
}
}
Did lot of research on the web and on stack... lots of user having this issue but none of their solution worked for me.
Any suggestions?
Thanks a lot.
Solution:
Using PARALLELS... be sure that your project is not on on "shared" space between the two OS.
I've been not able to execute the project in the mac folder.
Been not able to execute on shared space
Worked on Windows Only space.
Thanks.
Related
I was trying to input 'npm install #react-navigation/native-stack' In my vscode's terminal to install #react-navigation/native-stack but during installing, error occured.
The following is error message.
npm ERR! code 128
npm ERR! An unknown git error occurred
npm ERR! command git --no-replace-objects ls-remote ssh://git#github.com/react-navigation/native-stack.git
npm ERR! ERROR: Repository not found.
npm ERR! fatal: Could not read from remote repository.
npm ERR!
npm ERR! Please make sure you have the correct access rights
npm ERR! and the repository exists.
npm ERR! A complete log of this run can be found in:
npm ERR! path(my log files path)
my package.json file
{
"name": "userinterface",
"version": "1.0.0",
"main": "node_modules/expo/AppEntry.js",
"scripts": {
"start": "expo start",
"android": "expo start --android",
"ios": "expo start --ios",
"web": "expo start --web"
},
"dependencies": {
"#react-navigation/native": "^6.0.13",
"expo": "~46.0.9",
"expo-status-bar": "~1.4.0",
"react": "18.0.0",
"react-native": "0.69.5",
"react-native-screens": "~3.15.0",
"react-native-safe-area-context": "4.3.1",
"undefined": "react-navigation/native-stack"
},
"devDependencies": {
"#babel/core": "^7.12.9"
},
"private": true
}
I'm newbie for react-native and programming. so I don't know what to upload here. if you need more information to solve this problem, I will upload that.
It could be a compatibility issue. Try running
npm install npm#latest -g
and check again
I think there was a mistake in your package.json. It should be a package name following it's version. In this case it's should be
"dependencies": {
"#react-navigation/native": "^6.0.13",
"expo": "~46.0.9",
"expo-status-bar": "~1.4.0",
"react": "18.0.0",
"react-native": "0.69.5",
"react-native-screens": "~3.15.0",
"react-native-safe-area-context": "4.3.1",
"react-navigation/native-stack": "^6.9.0"
},
I am trying to deploy a parcel react app, with no backend on Heroku. The build keeps failing, I have tried everything on the internet. Here is the script & dependencies. Here is the error.
Error:
lscpu: failed to determine number of CPUs: /sys/devices/system/cpu/possible: No such file or directory
/tmp/build_c7ac30db/src/components/App.js:14:19: Cannot resolve dependency '../pages/a00auth/A01SignUp.js' at '/tmp/build_c7ac30db/src/pages/a00auth/A01SignUp.js'
12 |
13 | import errorReporting from '../exceptions/errorReporting';
> 14 | import SignUp from '../pages/a00auth/A01SignUp.js';
| ^
15 | import SignIn from '../pages/a00auth/A02SignIn';
16 | import OfflineMessage from '../components/OfflineMessage';
17 |
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! teziagents#1.0.0 heroku-postbuild: `parcel build ./src/index.html`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the teziagents#1.0.0 heroku-postbuild 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! /tmp/npmcache.05UZK/_logs/2021-09-23T09_57_29_536Z-debug.log
-----> Build failed
Scripts:
"scripts": {
"start": "parcel ./src/index.html",
"build": "parcel build ./src/index.html",
"postbuild": "workbox generateSW",
"predeploy": "rm -rf dist && npm run build",
"deploy": "gh-pages -d dist"
},
Dependencies:
"dependencies": {
"#reach/router": "^1.3.4",
"grommet": "^2.17.1",
"grommet-controls": "^3.0.1",
"grommet-icons": "^4.5.0",
"parcel-bundler": "^1.12.5",
"#parcel/transformer-webmanifest": "^2.0.0-beta.2",
"pouchdb": "^7.2.2",
"pouchdb-authentication": "^1.1.3",
"pouchdb-browser": "^7.2.2",
"pouchdb-core": "^7.2.2",
"pouchdb-find": "^7.2.2",
"react": "^17.0.2",
"react-dom": "^17.0.2",
"react-hook-form": "^7.7.1",
"styled-components": "^5.2.3",
"tslib": "^2.2.0"
},
Any help here is greatly appreciated. Have been breaking my head against this for a month now 😔
Heroku is made for backend applications. It's not able to build your application.
So, if you want to develop your react application there has to be using a nodejs wrapper (of the built application) which is more complicated but also doesn't work as fast as it can.
In this case, if you want to deploy a fast react application with almost no configuration you can use:
https://vercel.com/ - As simple as give access to your repo, specify the command and folder; configuration in the image https://pasteboard.co/LKodGrRHO00X.png
https://www.netlify.com/ - As simple as give access to your repo, specify the command and folder; configuration in the image https://pasteboard.co/WXecBxxJwylC.png
https://pages.github.com/
Or if you can build at your end and just upload the dist folder, you can also use:
https://firebase.google.com/products/hosting
I am trying to use React Native Navigation 5. I have added all the dependency but when i am adding
npm install react-native-gesture-handler it is giving the below error:
npm ERR! code ENOENT
npm ERR! syscall spawn git
npm ERR! path git
npm ERR! errno ENOENT
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t https://github.com/naver/hammer.js.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
Then i followed the below solution and downloaded the Github, save the path in System Variable but it did not work. Please suggest what wrong i am doing.
https://stackoverflow.com/a/23179102
My package.json
{
"name": "NavigationExample",
"version": "0.0.1",
"private": true,
"scripts": {
"android": "react-native run-android",
"ios": "react-native run-ios",
"start": "react-native start",
"test": "jest",
"lint": "eslint ."
},
"dependencies": {
"#egjs/hammerjs": "^2.0.17",
"#react-native-community/masked-view": "^0.1.6",
"#react-navigation/native": "^5.0.1",
"#react-navigation/stack": "^5.0.1",
"react": "16.9.0",
"react-native": "0.61.5",
"react-native-reanimated": "^1.7.0",
"react-native-safe-area-context": "^0.7.2",
"react-native-screens": "^2.0.0-beta.2"
},
"devDependencies": {
"#babel/core": "7.8.4",
"#babel/runtime": "7.8.4",
"#react-native-community/eslint-config": "0.0.5",
"babel-jest": "24.9.0",
"eslint": "6.8.0",
"jest": "24.9.0",
"metro-react-native-babel-preset": "0.56.4",
"react-test-renderer": "16.9.0"
},
"jest": {
"preset": "react-native"
}
}
It is working fine on mac but not working on Windows 10 Home.
This link helped me to get out of this issue: Here's a link
In short Download Git then follow the below steps:
Open Environment Variables
Edit Path
Find your git location that been installed in your device. Example like mine is C:\Program Files\Git\cmd
Add the git location to Path (make sure to add this to both user variables and system variables)
Apply the changes and restart your pc
Lastly, go back to your project and run npm install react-native-gesture-handler
This looks like a permission error. Please run your command line as a Administrator.
delete your node module and try again
npm install
I'm currently trying to setup CI through GitLab for my React app hosted on Firebase. I'm struggling to get past this point. There were some other post suggesting the use of sudo but the console told me the command was not found.
Any help would be greatly appreciated. Thanks you.
Here are my current configurations:
gitlab-ci.yml configuration file
image: node:10.15.3
cache:
paths:
- node_modules/
stages:
- build
- deploy
deploy_dev:
stage: deploy
script:
- echo "Deploying to staging environment"
- npm install -g firebase-tools
- firebase deploy --token $FIREBASE_DEPLOY_KEY --project $CI_ENVIRONMENT_NAME
environment:
name: dev
only:
- master
Package.json
{
"name": "react-app",
"version": "0.1.0",
"private": true,
"dependencies": {
"bootstrap": "^4.4.1",
"firebase": "^6.6.2",
"firebase-functions": "^3.3.0",
"moment": "^2.24.0",
"node-sass": "^4.13.1",
"react": "^16.12.0",
"react-beautiful-dnd": "^11.0.5",
"react-dates": "^20.3.0",
"react-dom": "^16.12.0",
"react-moment": "^0.9.7",
"react-perfect-scrollbar": "^1.5.3",
"react-router-dom": "^5.1.2",
"react-scripts": "^3.3.0",
"reactstrap": "^8.2.0",
"recompose": "^0.30.0"
},
"scripts": {
"start": "react-scripts start",
"build": "react-scripts build",
"test": "react-scripts test",
"eject": "react-scripts eject"
},
"eslintConfig": {
"extends": "react-app"
},
"browserslist": [
">0.2%",
"not dead",
"not ie <= 11",
"not op_mini all"
]
}
The console error indicating permission error
$ firebase deploy -m "Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID" --non-interactive --token $FIREBASE_DEPLOY_KEY --project $CI_ENVIRONMENT_NAME
⚠ functions: package.json indicates an outdated version of firebase-functions.
Please upgrade using npm install --save firebase-functions#latest in your functions directory.
=== Deploying to 'cmd-dev-bbdc4'...
i deploying functions, hosting
Running command: npm --prefix "$RESOURCE_DIR" run lint
> functions# lint /builds/cmdc/cmd/functions
> eslint .
sh: 1: eslint: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! functions# lint: `eslint .`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the functions# lint 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! /root/.npm/_logs/2020-02-03T01_51_09_788Z-debug.log
Error: functions predeploy error: Command terminated with non-zero exit code126
ERROR: Job failed: exit code 1
So through some experimentation I was able to determine that I had to cd into the 'functions' directory and also run NPM install. I guess this was a due to a fundamental misunderstanding of how Firebase projects are structured and of node packages.
I would love to learn more so if anyone share some reading about this, it would be appreciated.
Ended up with a script that look like the following.
deploy_dev:
stage: deploy
script:
- echo "Deploying to staging environment"
- npm install -g firebase-tools #--allow-root
- npm ci #--allow-root
- cd functions # required or would throw the "eslint: not found" error
- npm ci
- cd ..
- firebase use --token $FIREBASE_DEPLOY_KEY $CI_ENVIRONMENT_NAME
- firebase deploy -m "Pipeline $CI_PIPELINE_ID, build $CI_BUILD_ID" --non-interactive --token $FIREBASE_DEPLOY_KEY
environment:
name: dev
everyone. I try to deploy Reack full stack app from https://github.com/crsandeep/simple-react-full-stack
And it doesn't work. I read too many posts about deploying react to gcloud but there are simple apps and not full stack apps.
my packege.json, I took it from git
{
"name": "simple-react-full-stack",
"version": "1.0.0",
"description": "Boilerplate to build a full stack web application using React, Node.js, Express and Webpack.",
"main": "src/server/index.js",
"scripts": {
"build": "webpack --mode production",
"start": "npm run build && node src/server/index.js",
"client": "webpack-dev-server --mode development --devtool inline-source-map --hot",
"server": "nodemon src/server/index.js",
"dev": "concurrently \"npm run server\" \"npm run client\""
},
"author": "Sandeep Raveesh",
"license": "ISC",
"dependencies": {
"babel-polyfill": "^6.26.0",
"express": "^4.16.3",
"react": "^16.5.2",
"react-dom": "^16.5.2"
},
"devDependencies": {
"#babel/core": "^7.0.0",
"#babel/plugin-proposal-class-properties": "^7.0.0",
"#babel/preset-env": "^7.0.0",
"#babel/preset-react": "^7.0.0",
"babel-eslint": "^10.0.0",
"babel-loader": "^8.0.0",
"clean-webpack-plugin": "^1.0.0",
"concurrently": "^4.0.0",
"css-loader": "^2.0.0",
"eslint": "^5.0.0",
"eslint-config-airbnb": "^17.0.0",
"eslint-plugin-import": "^2.11.0",
"eslint-plugin-jsx-a11y": "^6.0.3",
"eslint-plugin-react": "^7.7.0",
"file-loader": "^3.0.0",
"html-webpack-plugin": "^3.2.0",
"nodemon": "^1.17.3",
"style-loader": "^0.23.0",
"url-loader": "^1.0.1",
"webpack": "^4.5.0",
"webpack-cli": "^3.0.8",
"webpack-dev-server": "^3.1.3"
}
}
my app.yaml I took it from google
env: flex
runtime: nodejs
I run in terminal
gcloud beta app deploy
And I have error
Updating service [default] (this may take several minutes)...failed.
ERROR: (gcloud.beta.app.deploy) Error Response: [9]
Application startup error:
> simple-react-full-stack#1.0.0 prestart /app
> npm run bundle
> simple-react-full-stack#1.0.0 bundle /app
> webpack --config webpack.config.js
sh: 1: webpack: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! simple-react-full-stack#1.0.0 bundle: `webpack --config webpack.config.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the simple-react-full-stack#1.0.0 bundle 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! /root/.npm/_logs/2019-12-04T18_45_03_238Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! simple-react-full-stack#1.0.0 prestart: `npm run bundle`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the simple-react-full-stack#1.0.0 prestart 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! /root/.npm/_logs/2019-12-04T18_45_03_252Z-debug.log
I don't understand what it need, I tried to add "npm install" and it doesn't work too.
How fix it?
Here is a community tutorial you can follow, get everything working as described first and then start making the desired edits.
Please make sure you are following the steps of "Preparing the app" section, as it seems like you are missing on of the mentioned steps.
npm init
npm install --save webpack express pug
As well as modifying package.json to include:
"scripts": {
"bundle": "webpack --config webpack.config.js",
"prestart": "npm run bundle"
}
Also note that:
Webpack must be listed in the dependencies of the package.json file,
as by default devDependencies are not installed when the app is
deployed to Google App Engine.
Also keep in mind that gcloud beta app deploy is still in BETA and may have changes without notice. So for what you are trying to achieve there is no need for using beta. Instead simply use gcloud app deploy.