Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to handle cases for non-standard import paths? #583

Open
gnohj opened this issue Nov 29, 2023 · 0 comments
Open

How to handle cases for non-standard import paths? #583

gnohj opened this issue Nov 29, 2023 · 0 comments

Comments

@gnohj
Copy link

gnohj commented Nov 29, 2023

I'm encountering an issue while trying to import a 3rd-party package using the following import statement:

import { xxx } from 'xxx:xxxx';

which results in the following error:

 馃巵  error '@gnohj/custom-package' 'xxx:xxxx' is imported by "src/index.ts" but the package is not specified in dependencies or peerDependencies

This 3rd-party package is correctly listed as a dependency in the package.json file of my shared package.

I've tried configuring tsconfig.json paths and using the imports field in package.json, but I haven't been able to resolve this issue successfully. I have a workaround to ignore the error, but a native solution would be better! Any guidance or insights would be greatly appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant