remix icon indicating copy to clipboard operation
remix copied to clipboard

How to support custom babel config for emotion show classname for run dev command

Open Caesar-APAX opened this issue 1 year ago • 3 comments

Aslo it need support @styled-coponents to show classname for run dev

Reproduction

https://github.com/Ranger-Theme/ranger-storefront-mui-remix

System Info

Mac os

Used Package Manager

pnpm

Expected Behavior

When i run dev command, the emotion shuld show the class name for StyledXXX

Screen Shot 2024-07-03 at 11 08 41 AM

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";

export default defineConfig({
  plugins: [
    react({
      jsxImportSource: "@emotion/react",
      babel: {
        plugins: ["@emotion/babel-plugin"],
      },
    }),
  ],
});
export default defineConfig({
  plugins: [
    remix({
      jsxImportSource: "@emotion/react",
      babel: {
        plugins: ["@emotion/babel-plugin"],
      },
    }),
  ],
});

Actual Behavior

Screen Shot 2024-07-03 at 11 12 33 AM

Not show the real className, just show axjs-xx className

https://dev.to/glocore/configure-emotion-with-your-vite-react-project-7jl

Caesar-APAX avatar Jul 03 '24 03:07 Caesar-APAX

@brophdawg11 Dou you support remix custom babel plugins?

Caesar-APAX avatar Jul 04 '24 00:07 Caesar-APAX

@n8agrin @freeman @dmarkow @brophdawg11 Any update? thanks

Caesar-APAX avatar Jul 17 '24 00:07 Caesar-APAX

Also wondering

Zigonja avatar Jul 30 '24 23:07 Zigonja

Thank you for opening this issue, and our apologies we haven't gotten around to it yet!

With the release of React Router v7 we are sun-setting continued development/maintenance on Remix v2. If you have not already upgraded to React Router v7, we recommend you do so. We've tried to make the upgrade process as smooth as possible with our Future Flags. We are now in the process of cleaning up outdated issues and pull requests to improve the overall hygiene of our repositories.

We plan to continue to address 2 types of issues in Remix v2:

  • Bugs that pose security concerns
  • Bugs that prevent upgrading to React Router v7

If you believe this issue meets one of those criteria, please respond or create a new issue.

For all other issues, ongoing maintenance will be happening in React Router v7, so:

  • If this is a bug, please reopen this issue in that repo with a new minimal reproduction against v7
  • If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support it can be considered for implementation

If you have any questions you can always reach out on Discord. Thanks again for providing feedback and helping us make our framework even better!

MichaelDeBoey avatar May 08 '25 22:05 MichaelDeBoey