prettier-eslint VS twin.examples

Use the other one, prettier-eslint this is so that the code goes through Prettier before ESLint and not the other way around causing it to show issues that will be fixed once ESLint fixes it.

Same, I can't stand some of prettier's opinions/style conversions and they refuse to add more options to their config file, so people literally have to make an entirely separate plugin just to deal with the issue of its config not being able to match your eslint config.

prettier-eslint

side note: you can use prettier-eslint (as opposed to the prettier eslint plugin) which runs prettier and then eslint --fix. that way you won't get annoyed by a shit ton red lines from eslint linting with prettier.

And I just ripped out my prettierrc/prettier recently, and still need some tweaking in this area, and might even add it it back. After looking at that plugin, it looks like it just DISABLES things in ESLint that Prettier handles, so you might have to add the prettier script and a .prettierrc config file. At least that is how I understand it. I was just looking at prettier's docs and saw this though - https://github.com/prettier/prettier-eslint, which seems like it might be what you are looking for.

Hey, I'm trying (and failing) to put together a codesandbox. I think it's easier to replicate the steps from here: https://github.com/ben-rogerson/twin.examples/tree/master/next-styled-components

well, this is exactly how it's set up in the twin.macro example repo with next.js, and it is working perfectly fine?

You can pretty much follow all the steps from this tutorial, until this point where it tells you to extend JSX with a jsx-pragma in front of every twin.macro import. The documentation underneath says the following:

Alright, I had my tools in place and it was time to start connecting the dots, so to speak. I kicked off a new TSDX project, installed Styled components, and then went on to try and set up twin.macro. However, I hit a snag there... In the Twin example repo, there was no Styled Components + Storybook example, so I configured what seemed to make sense. Then I went on to add some samples, imported them into a new Story, and tried to run Storybook. It didn't work as expected. Some of the code worked and other components that were using the tw syntax didn't:

the biggest would be as a plugin to compile/transpile other language macros for example twin-macro (styled components using tailwind syntax) https://github.com/ben-rogerson/twin.examples/tree/master/component-library-styled-components/packages/components