warungpintar / warung-config Goto Github PK

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.

Create a tsconfig package that all projects can extend from.

Tasks

• Create warung-config-tsconfig package in monorepo
• Publish first version

MIT License

Automate publishing canary releases every time the master branch is changed.

Reference: https://github.com/kata-ai/aksara-ui/blob/master/.github/workflows/publish.yml

Bringing tsconfig in line with already existing tsconfig files in other projects.

Set up Lerna for maintaining the warung-config monorepo.

Create Prettier config to automatically format code on save (or before commit using lint-staged).

Tasks

• Create warung-config-prettier package in monorepo
• Publish first version

Create and publish ESLint config for Warung Pintar which follows our coding styleguides.

Tasks

• Create warung-config-eslint package in monorepo
• Publish first version

Need to declare README, overall guide how does this repo work