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
{{ message }}
This repository has been archived by the owner on Dec 8, 2022. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: