import/no-relative-packages fix breaks in monorepo

After updating my eslint config and running it on a yarn workspaces monorepo, I found that a new rule was added: import/no-relative-packages. I like the rule as it prevents someone from relatively importing something from another package.

But in my case, I have some test utils in a folder at the root of the monorepo which is just a folder and not a namespaced package. I’m currently importing them (relatively) only from some Jest tests. I’m not sure how the fix works, but in this case it seems to be simply assigning the name of the root folder for the project as the absolute path base like:

../../../testConfig/utils (import path before)

npm-library/testConfig/utils (after the fix)

The problem is it doesn’t work since Node can’t resolve ‘npm-library’. Perhaps it does work when fixing a relative import from a namespaced package but I haven’t tried.

If there’s not way to resolve this automatically, maybe it be a good idea to add an exception to the configuration (like a regex/glob pattern to disable for certain files/directories).