Update readme.md for tailwind.config.js file

[if1eight0sty]

configuration of tailwind.config.js for (err: require not defined)

[thecrypticace]

@if1eight0sty What situation are you seeing this error in?

[if1eight0sty]

@thecrypticace Actually, there are not any specific situations for this.
lemme explain,

this is my project A, that uses require without any errors,
AND

this is my project B, that gives error, require is not defined. So, I have to change it to make it work

Thus, I have added an OR section in the readme for convenience, if anyone has the same issue.

[thecrypticace]

Hey, so the error you were seeing in your editor is not a runtime error. It's just a linter warning because your project was configured with type: "module" which requires the use of the import syntax.

I think we're going to hold off on updating the readme right now as we'd need to do that for all our plugins, and maybe even the docs on tailwindcss.com and we don't want to do that at the moment.

We're introducing support for a simplified plugin syntax. I'm not sure what release it'll end up in but it's already usable in our insiders build — though it is currently undocumented. And, once we ship this support in a release, it is likely we'll update our plugin readme files to the new syntax.

This new syntax will support string-based plugins which we'll load instead of you having to require them. This also means you won't have to fiddle around with require or import if you don't want/need to.

An example of the new syntax:

module.exports = {
  theme: {
    // ...
  },
  plugins: [
    "@tailwindcss/container-queries",
    // ...
  ],
}

More details about this can be found here: tailwindlabs/tailwindcss#12087

With that I'm going to close this but appreciate the PR anyway. If anyone runs into a similar situation they'll may end up finding this PR anyway which should help guide them.

Thanks!