Francois Massart
Francois Massart
I have kind of the same scenario here... My employer has around 20 websites in 20 repos. In order to avoid to duplicate the **"default/basic npm scripts"**, I made a...
I was able to make it work by performing a `process.chdir("./node_modules/company-private-tools/");` before calling `runAll(["clean:site", "clean:common"], {parallel: true, stdout: process.stdout});` Hope it helps others.
I would appreciate it too. It is kind of frustrating to be able to add only "static values" to the attributes of the injected `` elements...
👋 Hi @MarnixElling, I cannot reproduce your issue... Can you share a demo project or simply provide the markup causing the warning and the warning itself... The rule `tailwindcss/classnames-order` would...
Hi @alvis, can you provide a demo repo demonstrating what you are trying to accomplish ? Thanks
Hi, this one is tricky to fix, for now I would encourage you to use the workaround...
Hi @nonameolsson sorry for the delay 😅 I don't know much about trunk, I recently published a new beta version which should support Tailwind CSS up to 3.2.3 as well...
Version 3.7.0 has been released and it should fix the issue `npm i -D eslint-plugin-tailwindcss` or `npm i -D [email protected]` If the issue persists, please open a new ticket. Cheers.
Hi @Serator, please try `[email protected]` It'll probably not handle multiple depth of spread object but it may be sufficient for you. Let me know how it works for you.
Hi @boboldehampsink, could you provide a sample file with exhaustive cases in it in `.twig` ? It could simply be an issue related to configuration... Thanks