4 ms·
I mean obviously, don't use it. But as usual, devil's advocate: The behavior can change on any release The most popular React framework, NextJS, vendors a
by technion 3y ago
I mean obviously, don't use it. But as usual, devil's advocate:
The behavior can change on any release
The most popular React framework, NextJS, vendors a specific, unreleased version of React and their documentation recommends the use of APIs that have never been in a stable release. That's apparently accepted everywhere. This particular variable couldn't be any worse.
- jitl 3y agoA lot of the thingies you can access from it are only set in development builds of React, so you will just get “null” all the time in production. If you spend like 8 hours building around it without knowing that, you’ll be pretty sad how it breaks when you finally test in an optimized production build.
- samus 3y agoIf NextJS vendors that React version and then recommends using those APIs, then it can be argued to becomes part of the public interface. On the other hand, the scary-named property is clearly meant to discourage that in a language where locking things down is otherwise quite difficult.