@react-three/postprocessing 2.9.0 → 2.9.2

package/README.md

@@ -4,7 +4,12 @@
 [![Downloads](https://img.shields.io/npm/dt/@react-three/postprocessing.svg?style=flat&colorA=000000&colorB=000000)](https://www.npmjs.com/package/@react-three/postprocessing)
 [![Discord Shield](https://img.shields.io/discord/740090768164651008?style=flat&colorA=000000&colorB=000000&label=discord&logo=discord&logoColor=ffffff)](https://discord.gg/ZZjjNvJ)
 
-`react-postprocessing` is a [postprocessing](https://github.com/pmndrs/postprocessing) wrapper for [@react-three/fiber](https://github.com/pmndrs/react-three-fiber). This is not (yet) meant for complex orchestration of effects, but can save you [hundreds of LOC](https://twitter.com/0xca0a/status/1289501594698960897) for a straight forward effects-chain.
+`react-postprocessing` is a
+[postprocessing](https://github.com/pmndrs/postprocessing) wrapper for
+[@react-three/fiber](https://github.com/pmndrs/react-three-fiber). This is not
+(yet) meant for complex orchestration of effects, but can save you
+[hundreds of LOC](https://twitter.com/0xca0a/status/1289501594698960897) for a
+straight forward effects-chain.
 
 ```bash
 npm install @react-three/postprocessing
@@ -20,17 +25,29 @@ npm install @react-three/postprocessing
 
 #### Why postprocessing and not three/examples/jsm/postprocessing?
 
-From [https://github.com/pmndrs/postprocessing](https://github.com/pmndrs/postprocessing#performance)
+From
+[https://github.com/pmndrs/postprocessing](https://github.com/pmndrs/postprocessing#performance)
 
-> This library provides an EffectPass which automatically organizes and merges any given combination of effects. This minimizes the amount of render operations and makes it possible to combine many effects without the performance penalties of traditional pass chaining. Additionally, every effect can choose its own blend function.
+> This library provides an EffectPass which automatically organizes and merges
+> any given combination of effects. This minimizes the amount of render
+> operations and makes it possible to combine many effects without the
+> performance penalties of traditional pass chaining. Additionally, every effect
+> can choose its own blend function.
 >
-> All fullscreen render operations also use a single triangle that fills the screen. Compared to using a quad, this approach harmonizes with modern GPU rasterization patterns and eliminates unnecessary fragment calculations along the screen diagonal. This is especially beneficial for GPGPU passes and effects that use complex fragment shaders.
+> All fullscreen render operations also use a single triangle that fills the
+> screen. Compared to using a quad, this approach harmonizes with modern GPU
+> rasterization patterns and eliminates unnecessary fragment calculations along
+> 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 MSAA (multi sample anti aliasing), which is react-postprocessing's default, you get high performance crisp results w/o jagged edges.
+Postprocessing also supports srgb-encoding 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.
 
 #### What does it look like?
 
-Here's an example combining a couple of effects ([live demo](https://codesandbox.io/s/react-postprocessing-dof-blob-pqrpl?)).
+Here's an example combining a couple of effects
+([live demo](https://codesandbox.io/s/react-postprocessing-dof-blob-pqrpl?)).
 
 <a href="https://codesandbox.io/s/react-postprocessing-dof-blob-pqrpl?" target="_blank" rel="noopener">
 <img src="bubbles.jpg" alt="Bubbles Demo" />
@@ -38,7 +55,7 @@ Here's an example combining a couple of effects ([live demo](https://codesandbox
 
 ```jsx
 import React from 'react'
-import { EffectComposer, DepthOfField, Bloom, Noise, Vignette } from '@react-three/postprocessing'
+import { Bloom, DepthOfField, EffectComposer, Noise, Vignette } from '@react-three/postprocessing'
 import { Canvas } from '@react-three/fiber'
 
 function App() {
@@ -58,93 +75,5 @@ function App() {
 
 ## Documentation
 
-#### EffectComposer
-
-The EffectComposer must wrap all your effects. It will manage them for you.
-
-```jsx
-<EffectComposer
-  enabled?: boolean
-  children: JSX.Element | JSX.Element[]
-  depthBuffer?: boolean
-  disableNormalPass?: boolean
-  stencilBuffer?: boolean
-  autoClear?: boolean
-  multisampling?: number
-  frameBufferType?: TextureDataType
-  /** For effects that support DepthDownsamplingPass */
-  resolutionScale?: number
-  renderPriority?: number
-  camera?: THREE.Camera
-  scene?: THREE.Scene
->
-```
-
-#### Selection/Select
-
-Some effects, like Outline or SelectiveBloom can select specific objects. To manage this in a declarative scene with just references can be messy, especially when things have to be grouped. These two components take care of it:
-
-```jsx
-<Selection
-  children: JSX.Element | JSX.Element[]
-  enabled?: boolean
->
-
-<Select
-  children: JSX.Element | JSX.Element[]
-  enabled?: boolean
->
-```
-
-You wrap everything into a selection, this one holds all the selections. Now you can individually select objects or groups. Effects that support selections (for instance `Outline`) will acknowledge it.
-
-```jsx
-<Selection>
-  <EffectComposer autoclear={false}>
-    <Outline blur edgeStrength={100} />
-  </EffectComposer>
-  <Select enabled>
-    <mesh />
-  </Select>
-</Selection>
-```
-
-Selection can be nested and group multiple object, higher up selection take precence over lower ones. The following for instance will select everything. Remove the outmost `enabled` and only the two mesh group is selected. You can flip the selections or bind them to interactions and state.
-
-```jsx
-<Select enabled>
-  <Select enabled>
-    <mesh />
-    <mesh />
-  </Select>
-  <Select>
-    <mesh />
-  </Select>
-</Select>
-```
-
-#### Selective bloom
-
-Bloom is selective by default, you control it not on the effect pass but on the materials by lifting their colors out of 0-1 range. a `luminanceThreshold` of 1 ensures that ootb nothing will glow, only the materials you pick. For this to work `toneMapped` has to be false on the materials, because it would otherwise clamp colors between 0 and 1 again.
-
-```jsx
-<Bloom mipmapBlur luminanceThreshold={1} />
-
-// ❌ will not glow, same as RGB [1,0,0]
-<meshStandardMaterial color="red"/>
-
-// ✅ will glow, same as RGB [2,0,0]
-<meshStandardMaterial emissive="red" emissiveIntensity={2} toneMapped={false} />
-
-// ❌ will not glow, same as RGB [1,0,0]
-<meshBasicMaterial color="red" />
-
-// ❌ will not glow, same as RGB [1,0,0], tone-mapping will clamp colors between 0 and 1
-<meshBasicMaterial color={[2,0,0]} />
-
-// ✅ will glow, same as RGB [2,0,0]
-<meshBasicMaterial color={[2,0,0]} toneMapped={false} />
-```
-
-- [react-postprocessing exports](https://github.com/pmndrs/react-postprocessing/blob/master/api.md)
+- [react-postprocessing docs](https://docs.pmnd.rs/react-postprocessing)
 - [postprocessing docs](https://pmndrs.github.io/postprocessing/public/docs/)

package/dist/effects/Pixelation.d.ts

@@ -1,6 +1,6 @@
-import React from 'react';
+/// <reference types="react" />
 import { PixelationEffect } from 'postprocessing';
 export type PixelationProps = {
     granularity?: number;
 };
-export declare const Pixelation: React.ForwardRefExoticComponent<PixelationProps & React.RefAttributes<PixelationEffect>>;
+export declare const Pixelation: import("react").ForwardRefExoticComponent<PixelationProps & import("react").RefAttributes<PixelationEffect>>;

package/dist/effects/ScanlineEffect.d.ts

@@ -2,4 +2,5 @@
 import { ScanlineEffect, BlendFunction } from 'postprocessing';
 export declare const Scanline: import("react").ForwardRefExoticComponent<{
     blendFunction: BlendFunction;
+    density: number;
 } & import("react").RefAttributes<typeof ScanlineEffect>>;