Repository navigation
Accessing FormData (without using it) emits experimental warning #42792
Description
Activity
This is tricky to do, because the classes are defined in the
undicidependency (where there is no experimental warning), so we would have to make wrapper classes that emit in the constructor, but I can't find a good way to do that without loadingundici(and that has side-effects that breaks some of our tests).@nodejs/undici
We could consider removing the runtime warning for
FormDataaltogether (but keep the experimental status in the docs).Reacted by Matteo Collina and Tushar RupaniLet's remove the experimental warning from FormData.
Reacted by James M Snell, Jolly-Pirate, Oliver Haas and Jay Sistar- added a commit that references this issue
on Apr 24, 2022 - added a commit that references this issue
on Apr 25, 2022 - added a commit that references this issue
on Apr 28, 2022
Version
v18.0.0
Platform
Darwin Simens-MacBook-Pro.local 21.4.0 Darwin Kernel Version 21.4.0: Fri Mar 18 00:45:05 PDT 2022; root:xnu-8020.101.4~15/RELEASE_X86_64 x86_64
Subsystem
No response
What steps will reproduce the bug?
node -e FormDataHow often does it reproduce? Is there a required condition?
Always.
What is the expected behavior?
No experimental warning should be emitted by simple accessing the variable without using it, similar to accessing
fetchitself.What do you see instead?
Additional information
Like
typeof fetchnot emitting any warning,typeof FormDatashouldn't. Using it should emit, but not simply accessing the variable.