I've create a project using
yarn create nuxt-app <project-name>
Then chose to add tailwind to the app. When i run the app i get this though...
localhost:3000
I've i run the app on my laptop it works, but if i run it on the desktop it does not work. The gitignore are the same. I'm not sure what is wrong? I've placed a copy of my project here if someone could help me please.
I'd expect to see the nuxtjs logo...
It's just the default boiler plate stuff for a vue, nuxt with tailwind project.
https://www.dropbox.com/s/ljf8a0ixel9ij0n/kanri-frontend-main.zip?dl=0
I am very sure you just started the wrong project. Did you run the start command from the wrong folder maybe? The files you provided are the nuxt ones, there is nothing with next in them. Please double check you did the "npm run dev" or the yarn command or whatever you're using from the correct project folder.
Related
My vue project started throwing errors last night. At first I thought it was some sort of node issue because my project wasn't fully loading, which wasn't an issue before and I kept getting an audit issue about my cli plugin. I update node to the latest version and it uploaded fully once, then later it stopped loading and showing anything on the screen. This morning, I tried loading it through the vue cli instead of the terminal and noticed they had updated the vue cli plugin. I updated my vue cli plugin and tried to build my project but now I'm getting this error
"spawn vue-cli-service ENOENT"
can anyone help me with this error and what to do to get my vue project back up and running? Everything was up and running fine before this. Not really sure what is going on. I also have the following plugins running on my project, not sure if that may be impacting anything: vuetify, axios, vuex, vue router, and I have firebase and firestore, as well.
Thanks in advance for your help!
Please use the following link. It worked for me right away.
https://programmerah.com/solution-of-serve-with-message-spawn-vue-cli-service-enoent-395/
I ran all this in Windows shell
in CMD into the project directory (this is very important!!)
execute NPM install
re-import in the visualization panel. (I just ran "vue ui")
Prior to doing this I had installed node using windows installer and then the following from the powershell
npm update -g #vue/cli
npm install -g #vue/cli-service-global
restart if you need to, go to the project directory in powershell and "vue ui" without quotes and it worked after that. I was able to compile and run the project without any issues. Once the task is built, you may open a new tab and goto localhost:8080
best of luck! (it was a witch-hunt for me)
I have created ionic 4 new project using following command.
ionic start myApp tabs
Install angular
ng add #angular/pwa --project app
And build app
ionic build --prod
at 92%(92% chunk asset optimization TerserPlugin) it doesn't work, stop here and and gives attached error!
Can somone adivse?
I tried to do the same operation with other projects but it doesn't work.
node v 9.8.0
You don't need to install angular, its already part of an Ionic project. Maybe you are confusing things by doing this.
Try doing the steps above but without this line:
ng add #angular/pwa --project app
Also btw if you are posting errors, please copy paste them in as text. Your error is hard to read and half clipped off - do yourself a favour and make it easy for people to help you.
I have Vue app, created with vue-cli. This is semi-developed application. I want show to customer what we have now. So, I want to deploy what we have.
If I run script npm run build can I continue project development after building? What best practices for deploying not finished app?
P. S. I'm new in vue. I know, that my question can be stupid. Anyway, do not place minuses, please.
You need to buy a vps hosting and install node.js. That's all, you can deploy your app. Also you can make a simple back-end on node+express and put there your 'dist' folder after npm run build and this will be your demo app.
Yes. npm run build will build and package your app into the dist folder. Everything under your src folder will remain as it is. You can continue working on your app normally and build it as often as you want. There aren't really best practices for this. I would just make sure it doesn't touch production data until it's actually ready.
I'm building a PhoneGap app with PhoneGap build. I'd like to sync the app with my Git repository at BitBucket. The problem is that I ignore the files that are in my node_modules folder and the dist files that are generated by WebPack. So I want to automatically run an npm install and webpack before PhoneGap builds the app.
I have looked into hooks, and they seem like exactly what I need. However, I can't seem to get them to work. For example, I made a folder hooks/before_build and placed a test script in there that just echos back the word "test". But I don't see the output of that anywhere in the build log. I also added it specifically to my config.xml without any output.
It seems unusual that I haven't been able to find anywhere that explains this, but I can't seem to find anywhere.
Could anyone share how they have their build system set up, or provide relevant links?
I have been going through the react-native tutorial and ran
react-native init AwesomeApp as detailed in the FB page.
After many trials and errors in setting the correct permissions and path I was able to get the app running on IOS.
Awesome app is in a directory Projects
Now I want to create my own app in the same Projects folder and when I try
react-native init newApp I get
Looks like React Native project already exists in the current
folder. Run this command from a different folder or remove node_modules/react-native
I tried from a different folder and still get the same message.
What's the best way to resolve this, deleting the node_modules/react-native or is there another solution and why the same error in a different folder?
Had the same issue, the solution wasn't obvious and I find it nowhere on the Internet so I'm leaving it here.
You may have installed react-native globally. While you should install react-native-cli globally.
Having the first one installed makes typical react-native commads work (starting an app, linking native modules). The only difference is that init fails with above message. And IIRC calling react-native without arguments reveals the source of the problem with descriptive message that you've globally installed wrong package.
Edit:
On Windows also make sure to use CMD, not PowerShell. PowerShell was calling react-native binary (instead of react-native-cli) from SOMEWHERE (I don't know the source, I don't have it available globally, I removed every single globally installed package and it was still calling it (probably from some locally insalled copy)).
React Native development caused another issues too (can't remember the details, sorry) when used with Powershell, so just stick to CMD on Windows.
You were probably still in the AwesomeApp directory while running react-native init newApp.
Try cd .. back to the Projects directory and run react-native init newApp again.
You will then see newApp directory is created inside the Projects directory.
This error occurs when it is in a folder that you deleted. Try to cd to another folder, and it will work.
In the directory C:\\Users\YourUserName you have a file "nodemodules" and a file named "MyProjectName" .
you should delete nodemodules file.
it works for me!
I ran into this too, Make sure your folder does not have any node modules, if problem persists then install react-native-cli again globally using
yarn add global react-native-cli and then initialize your project.
using react-native init {name}.
I had the same error because in some parent directory was backuped "node_modules" directory.
Error resolved by rename it.
Hello for everyone this problem gonna be solved by became sudo user in your Mac if you're using macbook now. Then start to create your project one more time.
Thanks