I have been working on a nextjs project locally as I usually do, but all of a sudden, the website stopped working on localhost!
I kept getting this error in the console:
crbug/1173575, non-JS module files deprecated.
System and libraries versions:
OS: Ubuntu 18.04
Node: 14.15.1
Nextjs: 9.5.2
Chrome: 92.0.4515.131 (Official Build) (64-bit)
Firefox: 90.0.2 (64-bit)
start script: NODE_ENV=development node server.js
I have witnessed the same issue on both chrome and Firefox.
I have seen a lot of solutions for this problem, but nothing worked.
After a little debugging and commenting out many parts of the code, I managed to locate the issue.
Basically, it occurs on the backend; not the frontend.
There was an infinite loop that kept responses stuck. Fixing that issue, solved it for me.
Related
All over sudden I can not build my website created with Creative Tim any more due to issues with sass and node:
material-kit-react.scss?v=1.8.0
Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime (93)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1
There seam to be no working combination of them both. Tied every suggestions form GitHub but nothing has helped.
Ok, found a solution by downgrading node to v12 with the nvm manager
I am a complete newbie to all this.
I tried to install node.js 4 times and then again uninstalled it every time trying different things, thinking one of them would work.
The link to the question is-Cannot find runtime 'node' on PATH - Visual Studio Code and Node.js
After I typed $node --version in powershell terminal in VSCode (after installing node.js in C drive, defaulting to all recommended options in the setup) I get an error. I have uploaded the image of the error.
the error
Please tell me how to get node.js working with VSCode.
To get the version of Node, just type node --version in the terminal without the "$".
After upgrading to Angular version 11, unit tests now fail on Travis CI. Locally they do succeed (even after clean install with the same node, nvm and npm versions).
The error for all unit tests is the same -
Failed: fn.bind is not a function
TypeError: fn.bind is not a function
at newTrustedFunctionForJIT (node_modules/#angular/compiler/fesm2015/compiler.js:6845:1)
at JitEvaluator.evaluateCode (node_modules/#angular/compiler/fesm2015/compiler.js:6909:1)
at JitEvaluator.evaluateStatements (node_modules/#angular/compiler/fesm2015/compiler.js:6883:1)
Based on the error message, I would assume that the issue might be related to ngcc? Anyone had similar issue?
Today I had the same problem. It involved testing with ChromeHeadless.
I had old version of Chrome Headless 83.0.4103.97 installed in docker image. After updating it to latest version 88.0.4324.96 it started to work.
Additional here is the corresponding angular github issue.
Using Chrome >= 87 should fix the issue.
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.
Background: I am running tests in the Protractor framework against a website written in Angular using Firefox as the browser
The website initially loads with a Server-side render. The follow-up client-side render appears to get interrupted. Angular is available, but nothing in the Dom loads.
Asking Google hasn't helped(none of the Stackoverflow results appeared to be relevant). Didn't see any open issues or closed issues on the Protractor github which appeared to be relevant
I'm not sure what's relevant to the investigation, so starting information:
Firefox version: 65
geckodriver version: v0.24.0 [last]
protractor version: 5.4.1
framework: jasmine
directconnect = true
Has anyone resolved this issue before? Is there additional information which would be relevant. What have I missed? The same tests running against Chrome pass without issue