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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nissix plugin scope-packages on wow-demos #1

Merged
merged 1 commit into from
Oct 13, 2021

Conversation

deanshub
Copy link
Contributor

@deanshub deanshub commented Mar 3, 2021

Hi, I'm Nissix, the automated PR bot!

Wix is moving its internal packages to the @wix scope (but still in the internal registry). Publishing new unscoped internal packages is no longer allowed, and all existing packages are moving to @wix. This means changing package names, and also all usages of those packages to their @wix scope version.

This PR is an automatic codemod that moves all of your packages to @wix scope, and changes any usages (pacakge.json, imports, requires, etc..) to their @wix version.

‼️ This codemod is best-effort! Meaning it may not have found and fixed all usages, but it did change your package.jsons. So go over the changes carefully and test this version carefully

If you want to know why we don't support publishing unscoped to the internal registry, check out this article on Dependency Confusion

If you are unsure, need help or have questions, reach us at #wix-scope-migration

Error Log:
npx: installed 234 in 6.508s

Output Log:
Migrating package "wow-demos" in .

Migration from non scope to @wix/scoped packages

/tmp/452f43dec4f0b059bcdaa9e3c3c56e6b

replace unpkg & node_modules script tags in html and templates

animation-playground/index.html
animation-playground/index3.html

@ydaniv ydaniv merged commit 62f6343 into master Oct 13, 2021
@ydaniv ydaniv deleted the nissix-scope-packages-wow-demos branch October 13, 2021 20:42
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

Successfully merging this pull request may close these issues.

2 participants