Skip to content

Latest commit

 

History

History
127 lines (74 loc) · 5.86 KB

TRACK.md

File metadata and controls

127 lines (74 loc) · 5.86 KB

Track

Firebase: deprecated npm dependencies

In sample, when doing a fresh npm install, this shows up:

$ npm install
npm WARN deprecated [email protected]: this library is no longer supported
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797)
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: Please upgrade  to version 7 or higher.  Older versions may use Math.random() in certain circumstances, which is known to be problematic.  See https://v8.dev/blog/math-random for details.
npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated @manifoldco/[email protected]: This package has changed to openapi-typescript
...
...

We have made a decision not to rush and try to remove request from the codebase all at once as that will almost certainly introduce bugs. Instead we are moving away piece-by-piece as we fix other things.

Mentioned in KNOWN.md.

Firebase emulators: passing Security Rules debug() info to the clients

I've raised the idea in Firebase JS SDK #4793 and got the comment:

I filed an internal feature request for this matter, however we can't provide definite timelines [...]

Nothing's going to happen for that, in the Firebase Issues. It's a graveyard!

  •  Check again / ask ~ Jul 2021 2024
  •  Maybe move the matter to firebase-tools if making it takes time (it's currently in wrong place since not a matter for the JS client)

Jest requires --experimental-vm-modules

The Jest docs mention that --experimental-vm-modules is needed.

Track the Node.js issue, and see when we can strip the parameters.

Jest should not require --detectOpenHandles 🏓

This is about any Firebase gRPC using client. All we can do is wait, and track the Jest issue...

Work-around:

Have --detectOpenHandles in the Jest parameters.

Jest: tapping to timeouts

Firebase CLI: cribs about npm version

Note: I (Asko) "solved" this by going to Docker Compose and being able to dictate the Node versions, there.

Node.js: Native fetch

  • "Fetch API has landed into Node.js" (discussion; Feb 22)

    • Node 17.5 has it, but behind a feature flag: --experimental-fetch

  •  Track node.js releases; when it's been stable without needing the feature flag, for two major releases ;) we can let the undici imports go.

    • 18.4.0 has it, without a flag

Undici: fetch trouble with localhost

  • TypeError: fetch failed (closed; might still be valid?)

    Found a cure, for now (see config.js). Once the issue may be resolved, remove the cure.

    Note: They claim it cannot be undici. Would require more debugging... #notime