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

Rename packages to already existing package in @warungpintar scope #16

Closed
resir014 opened this issue Apr 22, 2022 · 0 comments · Fixed by #17
Closed

Rename packages to already existing package in @warungpintar scope #16

resir014 opened this issue Apr 22, 2022 · 0 comments · Fixed by #17
Assignees

Comments

@resir014
Copy link
Member

resir014 commented Apr 22, 2022

So it turns out that we've previously published the same configs that we have here. Let's publish these new packages over the existing ones, marking the changes as breaking (minor version bump since we're still at v0.x).

Suggestions

  • warung-config-eslint -> @warungpintar/eslint-config
  • warung-config-prettier -> @warungpintar/prettier-config
  • warung-config-tsconfig -> @warungpintar/typescript-config

Legacy package deprecations

  • @warungpintar/eslint-config-base + @warungpintar/eslint-config-typescript -> @warungpintar/eslint-config
    (unified config for both JS + TS)

Blockers

Access to npm org still needed.

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 a pull request may close this issue.

1 participant