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
As you can see, I'm trying to make external from the widget entry point and use it in extensions. So, when I start linting process it says:
~/widget/src/extensions/video-catcher/js/index.js
2:1 warning 'widget' should be listed in the project's dependencies. Run 'npm i -S widget' to add it import/no-extraneous-dependencies
This is more or less a duplicate of #479: no-extraneous-dependencies doesn't have enough metadata (yet) to know that widget isn't an actual dependency. Working on it! 😅
@benmosher, thanks for the answer! Good to hear, that development doesn't stop 👍 You could give me some extra details if you want a participant in this feature. I'd like to help if I can :)
Is there any card or issue with ideas about this feature?
I settled the plugin and a webpack resolver for my webpack-based project.
Here is my webpack config:
As you can see, I'm trying to make external from the
widget
entry point and use it in extensions. So, when I start linting process it says:because of the
But I'm totally sure that the resolver is trying to resolve it and
findExternal
returnstrue
here: https://github.com/benmosher/eslint-plugin-import/blob/master/resolvers/webpack/index.js#L95But resolver works because after I installed it I avoided warnings about aliases.
Any ideas why it doesn't use found external and makes warning about it?
The text was updated successfully, but these errors were encountered: