An add-on has a fixture in a package which is only for testing and dev setup.
This package has a devDependency.
On make lint imports from this dependency cannot be resolved.
Any recommendations for best practice on how to let linter know how to resolve imports from this dependency? Do I add an .eslintrc.js to the testing/dev package?
Just to be clear: The dependency is correctly installed. The dev setup is OK and running with this dependency / add-on. This is 100% as expected. Also acceptance tests and unit tests are OK. It's just the make lint which is failing with 'warning Unable to resolve path to module '@plone-collective/volto-bookmarks/components' import/no-unresolved'.
I do not expect anyone to look into the quite complex add-on testing scenario and dev set up with corresponding backend add-on, OpenSearch, etc involved.
I just think this is not uninteresting to test an add-on with another add-on involved.
So, if you are interested, see GitHub - rohberg/volto-searchkit-block at dev-setup (branch 'dev-setup')
failing job: Fix devDependency "@plone-collective/volto-bookmarks": "^3.0.2" · rohberg/volto-searchkit-block@58ca091 · GitHub