node 14 causing unknown issues for graphqljs - javascript

So I recently tried upgrading my node from 13 to 14, but afterwards I was having issues with graphql.
What happened was that I was forever "pending" whenever I sent a request to the server. The problem is, there's no errors being thrown.
I'm wondering if anyone has had any issues with graphql when upgrading from 13 to 14.
Packages used:
express-graphql
graphql
graphql-iso-date
graphql-query-builder-v2
graphql-type-json
graphql-upload
If you don't have any problems with node 14 and these two graphql packages, please let me know, as it's then other packages that are causing the issue. Thanks.
My current solution is to downgrade node (I'm currently on node 12 since brew doesn't seem to have node 13 yet).

There is a known issue in the pg module and NodeJS 14. Since pg-promise also uses this module - I suspect this is the problem.
The proposed solution is to make sure you have pg>=8.0.3 installed.
This can be done by
updating to pg-promise>=10.5.2 which already has the updated pg module as a dependency and/or
updating to pg>=8.0.3 in the dependencies if explicitly specified.
Also make sure that any other library depending on pg is up to date.

Related

Angular application won't run - Cannot read properties of undefined (reading 'write')

I have an angular application I haven't touched in a while. I haven't made any changes since the last time it was working. Now I need to modify a few things. But the application won't serve locally so I can't make the changes. I don't understand what's wrong.
The npm install worked just fine and I don't have any code errors preventing it from running. I get the following error message when trying ng serve, but it seem extremely unhelpful. Any ideas?
Unfortunately without an exact reproduction of your project this will be really hard to pin point, but looking at what is given in the screen shot and prior experience with similar issues, I think this could be an issue with your package.json. Newer versions of node and npm look for the carets symbol (^) in both your package.json and the installed modules' package.json. When found, it will install newer versions of the package without error. Then when you go to run the project, the typings will break and Angular will refuse to compile and you get errors like these.
I would recommend removing all carets in older Angular projects to prevent this from happening as it is common occurence even when upgrading from more modern versions (I had this happen to me when upgrading from Angular 13 to Angular 14). However, with Angular 1.7/AngularJS not being supported anymore, I would recommend that you look into upgrading or rewriting the project in a modern version of Angular or another modern framework that fits the projects needs.

How to fix VS Code unable to create a strapi app?

I'm Having an issue that ruins my entire development plans, And I don't think I'm even the problem!
There is an headless CMS program (open source) called Strapi, If you know the program then good, If not, Your more than welcome to try and tell me if you can help me with this problem.
I'm having trouble creating a Strapi app in VSCode.
The error that I'm receiving is:
You are running Node.js 18.4.0
Strapi requires Node.js >=14.19.1 <=16.x.x
Please make sure to use the right version of Node.
But, The fault isn't on me, I have 16.17.0 version of node installed, and without a trace of the 18.4 version specified on the error code.
I tried uninstalling node, Changing the dependencies in the launch.json file, Nothing worked!
So I Found the solution, the problem was with the version, the recommended 16.17.0 version of node not working with strapi, the 16.15.0 works actually.

How to solve Amplify backend-config.json does not exist issue

I upgraded Amplify CLI, but I discovered in my amplify/backend/backend-config.json file has disappeared after taking a day to discovered that. Then I have tried running amplify init again with the options to continue with my existing environment or new environment, and I have tried both but still got the same error
Error: File at path: 'C:\Users\BEN\documents\TinderClone\amplify\backend\backend-config.json' does not exist
What do I do to solve this error (to get the backend-config.json back).
I was able to solve this by using the amplify pull then navigating to the #current-cloud-backend and copying the file from there to the directory needed.
I've solved the issue after more than 24 hours of frustration looking for the solution.
In my C:\Users\BEN.amplify\bin I deleted the bin folder, and I upgraded the amplify CLI using:-
"curl -sL https://aws-amplify.github.io/amplify-cli/install-win -o install.cmd && install.cmd"
After the download and installation I restarted my system. That solved the backend-config.json does not exist issue.
I hope this works for you if you have this same issue.

Error: "Command "maximizeWindow" is not yet implemented" using webdriverIO v6

I have a project on webdriverIOv5 which I have tried to upgrade to version 6.
But when calling browser.maximizeWindow(), then I get this as an error:
ERROR #wdio/sync: Error: Command "maximizeWindow" is not yet implemented
Here is my demo project https://github.com/mareru/webdriverIO-shop-demo.
Does anybody know how to fix this?
I did find some similar references on gitter but according to them, this should work.
I don't get what am I doing wrong.
Thanks!
maximizeWindow was removed when chromedriver switched from json wire to W3C protocol and reimplemented a couple of versions ago.
Make sure to use the latest version of chromedriver. You have to configure selenium-standalone service according to https://webdriver.io/docs/selenium-standalone-service.html#configuration in your config https://github.com/mareru/webdriverIO-shop-demo/blob/master/src/wdio.conf.ts#L95
Verified in my own example repo https://gitlab.com/bar_foo/wdio-cucumber-typescript/-/blob/master/config/wdio.CHROME.conf.ts

Installing Nodejitsu

I have successfully installed NodeJitsu using NPM. However, anytime I attempt to run it I get the following error:
TypeError: Arguments to path.join must be strings.
It happens at line 204 in path.js
Any ideas?
We are working on release our toolset with node 0.10.0 support, you can use it with the last 0.8.x branch (0.8.22). We will publish a new version as soon as possible.
This issue is fixed internally but we are working on all the possible points of failure in node 0.10.0.
Stay tunned for updates!
If you need support you can join #nodejitsu on Freenode ;)

Categories

Resources