docs: cleanup references to apache-superset/superset-ui
#23796
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
SUMMARY
It seems like packages from
superset-frontend
used to live inapache-superset/superset-ui
, but the repository was archived, and content has been imported here.Unfortunately, they still contain multiple references to the legacy repository, including links in
package.json
that are used by npm. It means that published packages on npm are still linking to the archived repository saying to not use it anymore.To remove that confusion, I've renamed all references to
apache-superset/superset-ui
and cleaned up relevant fields inpackage.json
to better support a monorepo.