-
Notifications
You must be signed in to change notification settings - Fork 23
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: rename import @tutorialkit/test-utils
to test-utils
#273
base: main
Are you sure you want to change the base?
Conversation
Run & review this pull request in StackBlitz Codeflow. |
Internal packages should always use scoped package names. This is a security feature. But if that convention hasn't been followed elsewhere, let's not follow it here either. |
@AriPerkkio How is it a security feature? |
This could import But well, if this kind of convention isn't followed in other packages, it's fine to not follow it here either. |
I recommend to read this one as well if you haven't seen it earlier: https://medium.com/@alex.birsan/dependency-confusion-4a5d60fec610 |
Oh thanks for the pointers! Maybe we could use an import path that cannot be published then like starting with I don't like using the |
@AriPerkkio I finished reading both, thanks again for sharing! 🤩 The behaviour of |
That would work. I've seen |
This PR reverts the renaming of the import back to how it was:
test-utils
(was renamed to@tutorialkit/test-utils
in #141).This change aligns better with conventions we have in other repositories and also makes it easier to find what the import correspond to given the name of the package is
test-utils
and not@tutorialkit/test-utils
. Note that we could instead change that package name to be@tutorialkit/test-utils
but this is not a desirable change we want given it's not meant to be published.