npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@putout/plugin-react

v1.3.0

Published

🐊Putout plugin helps to migrate to new version of React

Downloads

56

Readme

@putout/plugin-react NPM version

The library for web and native user interfaces

(c) react.dev

🐊Putout plugin helps to migrate to new version of React. Not bundled.

Install

npm i putout @putout/plugin-react-hooks -D

Add .putout.json with:

{
    "plugins": ["react"]
}

Rules

Config

Here is list of rules:

{
    "rules": {
        "react/apply-create-root": "on",
        "react/remove-useless-provider": "on",
        "react/remove-useless-forward-ref": "on",
        "react/remove-implicit-ref-return": "on"
    }
}

apply-create-root

ReactDOM.render() was deprecated in March 2022 (v18.0.0). In React 19, we’re removing ReactDOM.render() and you’ll need to migrate to using ReactDOM.createRoot():

react.dev

Check out in 🐊Putout Editor.

❌ Example of incorrect code

import {render} from 'react-dom';

render(<App/>, document.getElementById('root'));

✅ Example of correct code

import {createRoot} from 'react-dom/client';

const root = createRoot(document.getElementById('root'));
root.render(<App/>);

remove-useless-provider

In React 19, you can render as a provider instead of <Context.Provider>:

react.dev

Check out in 🐊Putout Editor.

❌ Example of incorrect code

function App() {
    const [theme, setTheme] = useState('light');
    
    // ...
    return (
        <UseTheme.Provider value={theme}>
            <Page/>
        </UseTheme.Provider>
    );
}

✅ Example of correct code

function App() {
    const [theme, setTheme] = useState('light');
    
    // ...
    return (
        <UseTheme value={theme}>
            <Page/>
        </UseTheme>
    );
}

remove-useless-forward-ref

Starting in React 19, you can now access ref as a prop for function components: New function components will no longer need forwardRef. In future versions we will deprecate and remove forwardRef.

react.dev

Check out in 🐊Putout Editor.

❌ Example of incorrect code

const MyInput = forwardRef((props, ref) => {
    return (
        <input {...props} ref={ref}/>
    );
});

✅ Example of correct code

const MyInput2 = forwardRef(({value}, ref) => {
    return (
        <input value={value} ref={ref}/>
    );
});

remove-implicit-ref-return

Due to the introduction of ref cleanup functions, returning anything else from a ref callback will now be rejected by TypeScript. The fix is usually to stop using implicit returns.

react.dev

Check out in 🐊Putout Editor.

❌ Example of incorrect code

const a = (
    <div ref={(current) => (instance = current)}/>
);

✅ Example of correct code

function App() {
    const [theme, setTheme] = useState('light');
    
    // ...
    return (
        <UseTheme value={theme}>
            <Page/>
        </UseTheme>
    );
}

License

MIT