Faye 1.2.0 breaks Promise.js
See original GitHub issue
Top Results From Across the Web
faye/CHANGELOG.md at master - GitHub
Add client. · Restructure the JavaScript codebase around Node modules (require/exports) rather than globals · Update the Promise shim to reflect the standard...
Read more >RubyGems - faye - Versions diffs - 1.2.0 → 1.2.1 - Mend - Diffend
Potentially problematic release. This version of faye might be problematic. Click here for more details. Files changed (8) hide show.
Read more >Changelog | Meteor API Docs
Summary of breaking changes. As Node.js version was upgraded to a new major version we recommend that you review if your npm dependencies...
Read more >Promise.all() - JavaScript - MDN Web Docs
This returned promise fulfills when all of the input's promises fulfill (including when an empty iterable is passed), with an array of the...
Read more >Npm package installation error on other partition
... '/usr/bin/npm', 'i', '@supabase/supabase-js' ] 1 info using ... silly placeDep ROOT type@1.2.0 OK for: d@1.0.1 want: ^1.0.1 127 timing ...
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 Free
Top 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
I released a new patch version (3.2.2) in which I pinned down the Faye dependency on 1.1.2.
👍 Same here. Found that this had to do with Faye.