Doesn't seem to work with Node 14
See original GitHub issueWe’ve been using node-pg-pubsub in our project for quite some time. In an upgrade from Node 10 to Node 14 it stopped working. More specifically we stopped seeing the Successful retry attempt for pubsub
notices in the server log and no published messages were picked up.
Downgrading to Node 12 made it work again, and we left it like that with no further debugging.
Just wanted to let you know that there seems to be some issues with Node 14.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Node 14 LTS in App Service = 10.22.0 on build #3293 - GitHub
I have an App Service that is configured to use Node 14 LTS (Linux web app). If I webssh into it, it will...
Read more >node 14 causing unknown issues for graphqljs - Stack Overflow
My current solution is to downgrade node (I'm currently on node 12 since brew doesn't seem to have node 13 yet). javascript ·...
Read more >Installing Node.js v10 doesn't seem to work, insta...
We are using SonarScanner to scan our .NET Core applications during build. This tool has upgraded its required Node.js version to v10 ...
Read more >Set up Node.js on WSL 2 - Windows - Microsoft Learn
A guide to help you get your Node.js development environment set up on Windows Subsystem for Linux (WSL).
Read more >How do I downgrade node or install a specific previous ...
I have node installed, using brew. I want to use an earlier version of node. Online, I find instructions such as, for example:...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah, how stupid of me. We have 0.5.0 so far from the latest version. Sorry about that, will try with the latest and see if that resolves the problem.
No worries @bostrom! Great that it works now 👍