Skip to content
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.

Testing modules must import from production module's NPM package name #279

Open
Blackbaud-SteveBrush opened this issue Jun 9, 2020 · 1 comment

Comments

@Blackbaud-SteveBrush
Copy link
Member

The testing module should be self-contained and behave the exact same way as any other module. If you import types from your production module, you need to import it via the NPM package name: import { something } from '@skyux/my-package';. This can cause a chicken-and-the-egg situation where you may need to release the production module first, then release again with the testing module in place.

It would be nice to provide a way to alias the production module so that a testing module can reference something in the production module before it's released.

@Blackbaud-SteveBrush
Copy link
Member Author

The current workaround is to release the production module first, then write the testing module.

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

No branches or pull requests

1 participant