I am trying to deploy a new jHipster application to Tomcat using version 6.1.0. A previous app using older versions worked just fine. I changed my pom.xml to generate a war instead of a jar file. If I run the war file as "java -jar app.war" it works fine, but if I deploy the war file to Tomcat my browser shows error message related to npm.
I have tried both app.war and app.war.original. I have set my baseHref in webpack.common.js to match my context name.
Here is the browser response:
An error has occurred :-(
Usual error causes
You started the application from an IDE and you didn't run npm start or npm run webpack:build.
You had a network error while running npm install. If you are behind a corporate proxy, it is likely that this error was caused by your proxy. Have a look at the JHipster error logs, you will probably have the cause of the error.
You installed a Node.js version that doesn't work with JHipster: please use an LTS (long-term support) version, as it's the only version we support.
Building the client side code again
If you want to go fast, run ./mvnw to build and run everything.
If you want to have more control, so you can debug your issue more easily, you should follow the following steps:
...
Related
I am using the LTS version of NodeJS. The problem started with version node-v16.18.0-x64 and did continue with node-v18.12.0-x64.
What I am doing:
Developing Playwright test. I ran the test and NodeJS was working. After one minute, I rerun the test and NodeJS is no longer recognized in my OS.
The issue appears when I am using Cypress, so I think the issue is not related to the technology that I am using.
I checked the environment variable: It is there.
The workaround I am doing is to uninstall the NodeJS from the control panel and install it again. There is an option to repair the NodeJS installation. But when I try to use it, I receive an error message that the NodeJS is not installed on this OS.
I am using the Vaadin sping boot web app starter and everytime I run the application java file to start the web page, I always get
There was an unexpected error (type=Internal Server Error, status=500). java.lang.IllegalStateException: Failed to install Node"
Followed by hundreds of lines of error messages all related to either node or zip END header not found.
Even though I have Node.js installed on my Laptop.
I'm using JDK 18, Windows 10, IntelliJ community edition 2022.1.2 and Vaadin 22.
Any help on how to get my localhost up and running would be greatly appreciated.
Since you did not mention any build automation tool that you use, you can solve the problem by installing two missing tools (Node.js and npm) manually.
Go to https://nodejs.org/en/download
Choose and download installer
Make sure npm is also installed (select the option)
I decided to upgrade my version of nodejs from 8.11.1 to 10.15.3. I am running on Windows 10 so I downloaded v10.15.3-x64.msi file. I created a brand new Angular application from "ng new" command and I got the "HTTP ERROR 400" page with no error in the console.
I have cleared the cache, reboot the system and nothing helps. When I will go back to node JS version 8.11.1 everything starts to work again. The newest version of nodejs v11.11.0-x86.msi also doesn't work for me.
How this can happen and how can I get any information what is going on?
EDIT: this is not a duplication of any existing topics about upgrading NodeJS, because the new version is seen by the system and all components - see the console result in the screenshot I provided. After upgrading the NodeJs all my solutions based on that technology stoped working showing HTTP Error 400 page. After degrading to v8 everything starts working again.
The problem came back when I had to install newer version of node (12.14.1), so this time it worked. Additionally I deleted folders that prompted from runnig where npm command after deleting an old version.
I have just set up a TFS 2017 server and am trying to go through the CI tutorial at https://learn.microsoft.com/en-us/vsts/build-release/apps/nodejs/build-gulp?tabs=vsts but am having trouble on the Gulp task. I am getting the error "Not found node: null". I am using an ubuntu agent with the most recent versions of node, npm, and gulp installed. All the tasks are configured exactly as described in the tutorial.
The error usually means you have an environment issue , such as node couldn't captured by TFS build agent.
For the Default agent queue:
VSTS: Select Hosted VS2017. This is how you can use our pool of agents that have the software you need to build your app.
TFS: Select a queue that includes a Windows build agent.
Source Link
If you are working with linux build agent, you need to use windows build agent instead of ubuntu(linux build) agent.
If you are working with windows agent, make sure the node, npm, and gulp installed before TFS build agent configured, otherwise the new capability will not captured.
You need to reconfigure the build agent or restart VSO agent service. Besides make sure your working directory of Gulp task is getting set properly.
I ended up uninstalling and reinstalling nodejs and npm. I believe the problem was that TFS did not sense the node.js and npm capabilities because I originally installed them using nvm, so the second time around I installed using apt packages and everything worked fine.
I am new to nodejs.
As I am trying to install ejs via npm on my local windows system. But it gives me error invalid protocol: 192.168.1.201. I have attached the screen shot.
Earlier I was using the same PC on a corporate proxy. But recently we have removed all proxies from the system. After removing all proxy settings everything is working fine. But still on few places I am getting this error message.
I have tried almost all possible commands to remove proxy from everywhere. But still I am not able to install ejs. I am also facing the same problem while installing express framework in nodejs.
Now the issue has been resolved. It was related to proxy settings. Earlier I tried to remove all the proxy from system but wasn't getting any success.
After removing proxy from the windows registry it started working properly.