v3 RC

.eslintrc.json

@@ -10,8 +10,7 @@
     "plugin:prettier/recommended",
     "plugin:react-hooks/recommended",
     "plugin:import/errors",
-    "plugin:import/warnings",
-    "plugin:storybook/recommended"
+    "plugin:import/warnings"
   ],
   "plugins": ["@typescript-eslint", "react", "prettier", "react-hooks", "import"],
   "parser": "@typescript-eslint/parser",

.github/workflows/release.yml

@@ -20,25 +20,6 @@ jobs:
       - run: |
           yarn install --frozen-lockfile
           yarn release
-          yarn build-storybook
         env:
           NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-      # - uses: actions/upload-pages-artifact@v1
-      #   with:
-      #     path: ./storybook-static
-
-  # See: https://github.com/actions/deploy-pages
-  # deploy-job:
-  #   needs: release-job
-  #   permissions:
-  #     pages: write
-  #     id-token: write
-  #   environment:
-  #     name: github-pages
-  #     url: ${{ steps.deployment.outputs.page_url }}
-  #   runs-on: ubuntu-latest
-  #   steps:
-  #     - name: Deploy to GitHub Pages
-  #       id: deployment
-  #       uses: actions/deploy-pages@v1

CONTRIBUTING.md

@@ -15,14 +15,6 @@ You can also just [![Open in GitHub Codespaces](https://img.shields.io/static/v1
 
 Be sure your commit messages follow this specification: https://www.conventionalcommits.org/en/v1.0.0-beta.4/
 
-## Storybook
-
-If you're adding a brand new feature, you need to make sure you add a storybook entry, here's a few tips:
-
-- Keep the story simple & show the essence of the component, remember some people may be looking at using drei for the first time & it's important the stories are clear and concise.
-- Keep assets minimal (3D Models, textures) to avoid bloating the repository
-- If you think a more involved example is necessary, you can always add a codesandbox to the main README while keeping the story minimalistic
-
 ## Publishing
 
 We use `semantic-release` to deploy the package. Because of this only certain commits will trigger the action of creating a release:

README.md

@@ -42,7 +42,7 @@ From
 > the screen diagonal. This is especially beneficial for GPGPU passes and
 > effects that use complex fragment shaders.
 
-Postprocessing also supports srgb-encoding out of the box, as well as WebGL2
+Postprocessing also supports gamma correction out of the box, as well as WebGL2
 MSAA (multi sample anti aliasing), which is react-postprocessing's default, you
 get high performance crisp results w/o jagged edges.
 

docs/introduction.mdx

@@ -36,7 +36,7 @@ From
 > the screen diagonal. This is especially beneficial for GPGPU passes and
 > effects that use complex fragment shaders.
 
-Postprocessing also supports srgb-encoding out of the box, as well as WebGL2
+Postprocessing also supports gamma correction out of the box, as well as WebGL2
 MSAA (multi sample anti aliasing), which is react-postprocessing's default, you
 get high performance crisp results w/o jagged edges.