All of my next apps are getting stuck at event - compiled successfully when I try and run them using yarn dev. Everything from existing apps I've used before to brand new apps I literally make just for trying this fresh.
I've tried deleting node_modules and yarn.lock, running yarn again, then running yarn dev. No dice. I also updated node js to latest and tried a few iterations of the above, including some with a 'yarn build` step to see if that did anything. No luck.
Assuming it's some kind of machine config that got messed up, but I can't for the life of me figure out what it is. Ideas?
replace with it in package.json
“dev”: “next dev -p 1234",
Related
I've cloned a nextjs example repo locally, and tried to run it using npm run dev, but it's not finding "next" as a command?
sh: next: command not found
I googled it, suggestions seemed to be that I should run
npm i -g create-next-app
Which I did, but still get the same error?
How can I resolve this?
For my particular case, I forgot to run npm install in the repo I'd just cloned :D
Once I did that, running npm run dev worked fine and found next.
But I suspect in general if you're trying to run a cloned repo based on npm, and get a similar response, you may simply have forgotten to install your dependencies, like I did.
Note that this can also happen for an existing project if you have some script that removes the node_modules folder as part of a cleanup process (which I do as well)
I try so many time but it's not working,
I try yarn install to install the yarn first, but it's not installing.
then I try yarn add and then yarn install, but still it's not working. I try next dev. cause I was thinking maybe that's how a next.js file open. but it's still not working.
give me a solution please
and one things, I was trying to create an next.js file but it's not opening. I try this code
yarn create next-app myapp
but it's not working, it's says this error
Usage Error: The nearest package directory (C:\Users\Intel Pc\Downloads\New folder\myapp) doesn't seem to be part of the project declared in C:\Users\Intel P
part of the project declared in C:\Users\Intel Pc.
- If C:\Users\Intel Pc isn't intended to be a project, remove any yarn.lock and/or package.json file there.
- If C:\Users\Intel Pc is intended to be a project, it might be that you forgot to list Downloads/New folder/myapp in its workspace configuration.myapp in its workspace configuration. ly separate project (not even a workspace), crea
- Finally, if C:\Users\Intel Pc is fine and you intend Downloads/New folder/myapp to be treated as a completely separate project (not even a workspace), create an empty yarn.lock file in it.
ev] [-i,--interactive] [--cached] [--mode #0] ..
$ yarn add [--json] [-E,--exact] [-T,--tilde] [-C,--caret] [-D,--dev] [-P,--peer] [-O,--optional] [--prefer-dev] [-i,--interactive] [--cached] [--mode #0] ...
Aborting installation.
yarn add --exact --cwd C:\Users\Intel Pc\Downloads\New folder\myapp react react-dom next has failed.
this image for my existing next.js app which I trying to open locally using yarn but it's not working
I'm deploying my Meteor app with mup from a Windows 10 box to a Digital Ocean VPS. Latest version of mup, latest version of meteor, app runs fine on Windows and the app deployed and ran fine before adding node-uber NPM. I see the following error in the logs when the app tries to start:
npm ERR! enoent ENOENT: no such file or directory, chmod '/bundle/bundle/programs/server/npm/node_modules/node-uber/node_modules/sshpk/bin\sshpk-conv'
Obviously the problem is with the backslash in the filename, but not sure where that is coming from or how to fix it. It isn't referenced in the package.json for node-uber. I've tried editting the package.json for sshpk on the Windows side, but that doesn't make any difference. I can't edit the file in the Docker container because the container keeps restarting and kicking me out.
Anyone have any suggestions on how to fix this, perferably permanently so I don't have to jump through hoops every time I deploy?
Actually manually editting the package.json file does solve the problem. Turns out I have multiple copies of sshpk installed because the parent NPMs are specifying specific versions as being required.
So the "fix" for this problem is the edit the "bin" section of the sshpk package.json file to flip the "\" to "/", save and rerun mup deploy.
Sigh...
I have just started exploring kibana 4. I am trying to make few UI modifications like removing the kibana icon in the nav bar. After making the changes,we need to prepare a build. I went through the 'CONTRIBUTING.md' file under kibana repo, where they have provided instructions on how to prepare a build. But it takes some time(10 to 15 min) to prepare a build after the changes.Is there any way where i can make the changes and see if the changes are working fine before making a build ?
If you execute grunt dev instead of grunt build, you will start a development server where each change in the code you do will be reflected. After executing it, you just have to go to your browser and enter in http://localhost:5601.
EDIT: It looks like now it's different than when I used to work on it. Try with npm start. Better to check the instructions in the source by the way: https://github.com/elastic/kibana/blob/master/CONTRIBUTING.md
I am using Kibana 4.3-snapshot.Not sure what was the issue.I cloned a fresh copy from here : https://github.com/elastic/kibana.git
Ran the following commands and could see the development server running.
nvm install 0.12
npm install
npm start
#Pigueiras Thank you
I am following the installation guidelines as described on mean.js.org Everything seemed to install fine. I have all prereqs installed. I ran npm install after cloning the github repo and then tried to run grunt and I didnt get any errors however It seems to just be stalling on the command line. Last message on the command line is the "debugger is running on port 5858" and then it just sits there.
After some time the message [nodemon] watching 51,839 files - this might cause high cpu usage. To reduce use "--watch" comes up. I am on windows 10 and have all the latest versions of node,npm,grunt and mean.js. I am running the command line as admin.
Mean.js should be running on localhost:3000 but it is not.
This is intended.
There is an application invoked by the grunt command and running in background, watching your files for changes. In default configuration: nodemon and grunt-watch.
This will execute specific tasks based on the files you edited, such as linting JS files or compiling LESS files.
The cmd will probably show something when you edit files in the projects directory.