You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
c289f18 added no-hide-core-modules rule.
This rule disallows require() expressions and import declarations if those import a third-party module which has the same name as core modules. Especially, if you depend on such modules indirectly and npm flattens dependencies, you can depend on such third-party modules before as you know it. This might cause unintentional behaviors.
17c8ae0 fixed the behavior of no-deprecated-api rule about indirect dependencies. The no-deprecated-api rule has ignored deprecated APIs if a code imports the third-party module which has same name as a core module. However, I found it can cause confusing because of indirect dependencies and flatting dependencies.
Now, The no-deprecated-api rule does not ignore deprecated APIs even if a code imports the third-party module which has same name as a core module except it's in your package.json explicitly.
If you want to revive old behavior, please set ignoreIndirectDependencies: true option.