Merge pull request #618 from thebuilder/feat/switch-to-pnpm

Author: thebuilder

.github/workflows/release.yml

@@ -9,16 +9,20 @@ jobs:
     name: Release
     runs-on: ubuntu-latest
     steps:
-      - name: Checkout
-        uses: actions/checkout@v3
+      - uses: actions/checkout@v3
+      - name: Install PNPM
+        uses: pnpm/action-setup@v2
+        with:
+          version: 7
       - name: Setup Node.js
         uses: actions/setup-node@v3
         with:
           node-version: 18
+          cache: 'pnpm'
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: pnpm install
       - name: Build
-        run: yarn build
+        run: pnpm build
       - name: Release
         env:
           GH_TOKEN: ${{ secrets.GH_TOKEN }}

.github/workflows/test.yml

@@ -12,16 +12,20 @@ jobs:
 
     steps:
       - uses: actions/checkout@v3
+      - uses: pnpm/action-setup@v2
+        with:
+          version: 7
       - name: Use Node.js ${{ matrix.node-version }}
         uses: actions/setup-node@v3
         with:
           node-version: ${{ matrix.node-version }}
+          cache: 'pnpm'
       - name: Install dependencies
-        run: yarn --frozen-lockfile
+        run: pnpm install
       - name: Lint
-        run: yarn lint
+        run: pnpm lint
       - name: Test
-        run: yarn test
+        run: pnpm test
         env:
           CI: true
       - name: Build

.gitignore

@@ -1,6 +1,5 @@
 .vscode
 .cache
-.docz
 node_modules
 reports
 example
@@ -11,10 +10,10 @@ nuget
 npm-debug.log*
 .DS_store
 .eslintcache
-.stylelintcache
 .idea
 .tern
 .tmp
 *.log
+storybook-static
 test-utils.js
 test-utils.d.ts

.npmignore

@@ -17,15 +17,13 @@ npm-debug.log
 .tmp
 .eslintignore
 .flowconfig
-.travis.yml
-.babelrc
 .editorconfig
-.storybook
-yarn.lock
+storybook/.storybook
+pnpm-lock.yaml
 
 # Project files
 coverage
-stories
+storybook/stories
 tests
 example
 jest-setup.js

.storybook/main.js

@@ -0,0 +1,86 @@
+# Contribution Guidelines
+
+Welcome to `react-intersection-observer`! I'm thrilled that you're interested in
+contributing. Here are some guidelines to help you get started.
+
+The codebase is written in TypeScript, and split into two packages using PNPM
+workspaces:
+
+- `react-intersection-observer` - The main package, which contains the
+  `useInView` hook and the `InView` component.
+- `storybook` - A Storybook project that is used to develop and test the
+  `react-intersection-observer` package.
+
+## Development
+
+Start by forking the repository, and after cloning it locally you can install
+the dependencies using [PNPM](https://pnpm.io/):
+
+```shell
+pnpm install
+```
+
+Then you can start the Storybook development server with the `dev` task:
+
+```shell
+pnpm dev
+```
+
+## Semantic Versioning
+
+`react-intersection-observer` follows Semantic Versioning 2.0 as defined at
+http://semver.org. This means that releases will be numbered with the following
+format:
+
+`<major>.<minor>.<patch>`
+
+- Breaking changes and new features will increment the major version.
+- Backwards-compatible enhancements will increment the minor version.
+- Bug fixes and documentation changes will increment the patch version.
+
+## Pull Request Process
+
+Fork the repository and create a branch for your feature/bug fix.
+
+- Add tests for your feature/bug fix.
+- Ensure that all tests pass before submitting your pull request.
+- Update the README.md file if necessary.
+- Ensure that your commits follow the conventions outlined in the next section.
+
+### Commit Message Conventions
+
+- We use
+  [semantic-release](https://github.com/semantic-release/semantic-release) to
+  manage releases automatically. To ensure that releases are automatically
+  versioned correctly, we follow the
+  [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
+  Conventions. This means that your commit messages should have the following
+  format:
+
+`<type>: <subject>`
+
+Here's what each part of the commit message means:
+
+- `<type>`: The type of change that you're committing. Valid types include
+  `feat` for new features, `fix` for bug fixes, `docs` for documentation
+  changes, and `chore` for changes that don't affect the code itself (e.g.
+  updating dependencies).
+- `<subject>`: A short description of the change.
+
+### Code Style
+
+`react-intersection-observer` uses [Prettier](https://prettier.io/) for code
+formatting. Please ensure that your changes are formatted with Prettier before
+submitting your pull request.
+
+### Testing
+
+`react-intersection-observer` uses [Vitest](https://vitest.dev/) for testing.
+Please ensure that your changes are covered by tests, and that all tests pass
+before submitting your pull request.
+
+You can run the tests with the `test` task:
+
+```shell
+pnpm test
+```

.storybook/preview-head.html

@@ -1,6 +1,6 @@
 The MIT License (MIT)
 
-Copyright (c) 2022 React Intersection Observer authors
+Copyright (c) 2023 React Intersection Observer authors
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal