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
My understanding of this rule is that it's meant to prevent packages in the monorepo from importing files that exist locally, but would not be present after publishing to NPM.
It's also preventing valid internal imports of files that we know do get published to NPM, e.g. anything that is listed in the files array of package.json. For example if we know that package-a has files: ["lib"] in it's package.json, we should be able to tell that an import like import foo from 'package-a/lib/foo.js' is safe.
Would you be open to a flag that allowed these sort of internal imports?
The text was updated successfully, but these errors were encountered:
My understanding of this rule is that it's meant to prevent packages in the monorepo from importing files that exist locally, but would not be present after publishing to NPM.
It's also preventing valid internal imports of files that we know do get published to NPM, e.g. anything that is listed in the
files
array of package.json. For example if we know thatpackage-a
hasfiles: ["lib"]
in it's package.json, we should be able to tell that an import likeimport foo from 'package-a/lib/foo.js'
is safe.Would you be open to a flag that allowed these sort of internal imports?
The text was updated successfully, but these errors were encountered: