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
I have my own "SDK" package which has a dependency of a popular ORM package.
I can installed my SDK package in a project, and I can import the ORM package and use it, however, autocomplete, and suggestions when i write a method belonging to the ORM hasn't yet been imported, simply do not work, unless I add the ORM package explicitly to my projects package.json, which seems a bit redundant?
Is there anything I can add to my project package.json file to get it working?
The text was updated successfully, but these errors were encountered:
I think it's intended behavior - dependencies specify which packages are required by app/package, but their transitive dependencies are implementation detail and consumers should not rely on them, as they can be removed/updated to new major/replaced in any deoendency update.
In your case you should add it to package.json to make your intent explicit, re-export subset of ORM API from SDK to control what consumers should have access to, use it as peerDependencies in SDK if consumers are expected to use ORM anyway.
I have my own "SDK" package which has a dependency of a popular ORM package.
I can installed my SDK package in a project, and I can import the ORM package and use it, however, autocomplete, and suggestions when i write a method belonging to the ORM hasn't yet been imported, simply do not work, unless I add the ORM package explicitly to my projects package.json, which seems a bit redundant?
Is there anything I can add to my project package.json file to get it working?
The text was updated successfully, but these errors were encountered: