Remix will rebuild, but if you compare both root.js files (build and build-old), you'll see the filename stays the same even though the import for tailwind.css has changed. Now add a new Tailwind class to your route and save. Then rename /public/build to /public/build-old. To reproduce, have a clean /public/build folder. ![]() But you can't rely on that on production. I'm having difficulty with differences between client-side and server-side rendering of styles in Material-UI components due to classNames being assigned differently. Unique identifier of the component in a namingContainer. □ The only way to work around this in dev, is to disable caching in your dev tools. TabView is a tabbed panel component featuring client side tabs, dynamic content loading with ajax and content transition effects. But the tailwind URL will change and will generate a bundle with the new file path, but with the SAME root hash! And since the /public/build folder is immutable, it will never download the new root file. For instance in my code detail page, I have done that like below. As a solution, i have implemented dynamic content approach checking some state values before rendering the element. to a project from the Start Page only removes the link to the project and does not. I was rendering this component on my pages and getting this warning. Enterprise Architect is an intuitive, flexible and powerful UML. So if your root route imports the tailwind.css file from app, the source never changes. So we have a mismatch here in the DOM and we get this warning. It looks like when esbuild compiles the route file, it generates the hash based on the contents of the original source, not the bundled output. Server: "/build/_assets/tailwind-UF2CZ54Y.css" Client: "/build/_assets/tailwind-GCIKYTPB.css ![]() Server: "/build/_assets/tailwind-DGHXG3YF.css" Client: "/build/_assets/tailwind-JUD5S62U.css"Īt RemixCatchBoundary ( at Remi圎rrorBoundary ( at RemixRoute ( at Routes ( at Router2 ( at RemixCatchBoundary ( at Remi圎rrorBoundary ( at Remi圎ntry ( at RemixBrowser ( I think I figured out why we're getting the error Warning: Prop href did not match.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |