Publish a codemod to migrate away from the deprecated "styled-components/native" imports

It’d be great to write a babel-codemod that quickly rewrites all imports and requires from styled-components/native to just styled-components;

Examples include:

// in
import /* ... */ from 'styled-components/native';
require('styled-components/native');

// out
import /* ... */ from 'styled-components';
require('styled-components');

Starting point would be the babel-codemod repo: https://github.com/square/babel-codemod

Here’s a good example of how to write a babel-codemod plugin: https://github.com/kentcdodds/babel-codemod-example

And finally this is how we target imports/requires in our babel plugin:

• https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/index.js#L12-L14
• https://github.com/styled-components/babel-plugin-styled-components/blob/master/src/visitors/assignStyledRequired.js#L4-L11

Hope this helps someone to get started with contributing to styled-components ❤️

The codemod should probably live in its own little repo that we can migrate to the styled-components org 💟

[RIP21]

@philpl I wrote ramda-codemod with almost the same approach and it worked well for over 500+ files with no issues at all. I think it’s quite safe to do it this way. This codemod is not a rocket science. So changing it to something more sophisticated is preliminary optimization and overengineering IMO, somebody will tell us if there will be issues. (I would personally just run search and replace against my project dir in IDE for such migration)

About TS, by default, js-codeshift is running against .js files. So .ts files will not be touched until user say so using extensions flag like: --extensions ts,js,jsx,tsx.

[probablyup]

@bbuckland That’s great! Want to add it to the RN section of the website?

(anyone else is welcome to do the same for their versions)