@dandedotdev is attempting to deploy a commit to the timlrx's projects Team on Vercel.

A member of the Team first needs to authorize it.

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Thanks for the PR. Seems like the changes might have affected the code block styles.

New:

Previous:

I'd like to apologize for my carelessness. Thank you for checking the actual applied styles for me.

In 03a8ec5, I revised the selector for code:

& :where(code):not(.code-highlight)

I think it might be better than:

& :where(code):not(pre code)

From the perspective of specificity

However, if the template migrates to another code-highlighting tool in the future, this might not work. (The classname is added by the generator of rehype-prism-plus.)

I also took the screenshots:

Light Theme	Dark Theme

Thank you again for your kindness and attention. I'll spend more time making the output CSS of both settings the same.

After scanning the output file of Tailwind v4, I found some use of pre code. Hence, I think it's okay.

I also corrected a mistake I made, in the content in the original tailwind.config.js:

module.exports = {
  theme: {
    extend: {
      typography: ({ theme }) => ({
        DEFAULT: {
          // ...
        invert: { // HERE
         // ...
        },
      }),
    },
  },
  plugins: [require('@tailwindcss/forms'), require('@tailwindcss/typography')],
}

...is for .prose-invert, so I corrected it.

There are still a few differences between the Tailwind output of my PR and that of the main branch. Sadly, for now, there is no way to get a similar output of @tailwindcss/typography by Tailwind v4. At least, there are no style conflicts.

Thanks, this looks good to me!