readme updates

Author: AlemTuzlak

README.md

@@ -7,9 +7,9 @@
 ![npm](https://img.shields.io/npm/dw/open-source-stack?style=plastic)
 ![GitHub top language](https://img.shields.io/github/languages/top/forge42dev/open-source-stack?style=plastic)
 
-Full starter stack to develop CJS/ESM compatible npm packages with TypeScript, Vitest, ESLint, Prettier, and GitHub Actions.
+Full starter stack to develop CJS/ESM compatible npm packages with TypeScript, Vitest, Biome, Prettier, and GitHub Actions.
 
-Detailed overview of the stastack:
+Detailed overview of the stack:
 https://youtu.be/ABRpwxLdGho
 
 Deploy your open-source project to npm with ease, with fully covered bundling, testing, linting and deployment setup out of the box,
@@ -24,32 +24,36 @@ Build your own open-source project today! 🚀
 - **Biome**: Biome statically analyzes your code to find issues and formats your code with a consistent, opinionated style.
 - **GitHub Actions**: Automate your workflow from idea to production.
 - **tsup** - Zero-config bundler for tiny TypeScript libraries.
+- **Changeset** - A way to manage your versioning and changelog with a focus on monorepos.
+- **pnpm workspaces** - A way to manage multiple packages in a single repository.
 
 ## Features
 
 - **ESM/CJS ready** - Write your code in TypeScript and publish it as ESM and CJS with 0 configuration.
 - **Are The types wrong? ready** - Passes all the checks for typings on https://arethetypeswrong.github.io/ by default.
 - **ESM/CJS test apps setup** - Test your package in both ESM and CJS environments already setup for you.
 - **Test runner setup** - Test your open source package with Vitest already setup for you.
-- **Linting setup** - Lint your code with ESLint and Prettier already setup for you.
+- **Linting setup** - Lint your code with Biome already setup for you.
 - **GitHub Actions setup** - Automate deployments to npm by using GitHub Actions.
+- **Changeset versioning & automation** - Automate releases with Changeset and GitHub Actions.
 
 ## Setup
 
 1. Use this template to create a new repository.
 2. Clone the repository.
 3. Change the package name in `package.json`.
 4. Change the `open-source-stack` dependency in your test-apps to your name
-5. Install the dependencies with `npm install`.
-6. Change the `repository`, `bugs`, and `homepage` fields in `package.json` to your github repo.
-7. Change the license if required.
-8. Add the NPM_TOKEN secret to your GitHub repository.
-9. Start coding!
+5. Change the `open-source-stack` folder name in packages to your package name
+6. Install the dependencies with `npm install`.
+7. Change the `repository`, `bugs`, and `homepage` fields in `package.json` to your github repo.
+8. Change the license if required.
+9. Add the NPM_TOKEN secret to your GitHub repository.
+10. Allow GitHub Actions to create and approve pull requests. (Settings -> Actions -> Workflow permissions)
+11. Start coding!
 
 ## Scripts
 
-- `npm run build` - Build the package.
-- `npm run test` - Run the tests.
-- `npm run lint` - Lint the code.
-- `npm run dev` - Start the package and ESM test app in watch mode for development.
-- `npm run dev:cjs` - Start the package and CJS test app in watch mode for development.
+- `pnpm run build` - Build the package(s).
+- `pnpm run test` - Run the tests.
+- `pnpm run check` - Lint the code.
+- `pnpm run dev` - Start the package(s) and ESM/CJS test app in watch mode for development.