Note that I suspect that this issue is most likely very hard/impossible to fix, but I thought I'd create this issue for people coming after me pondering with the same issue.
Node's permission based permissions is enforced by adding the --permission flag when running Node.
To get TailwindCSS up and running you also need to add:
--allow-addons
--allow-child-process
--allow-worker
The most problematic security issue in the above is (I think) --allow-child-process which gives Tailwind's config/plugins more or less full OS access. Given the error message I get, I suspect this is due to how you load lightningcss.
Note that I suspect that this issue is most likely very hard/impossible to fix, but I thought I'd create this issue for people coming after me pondering with the same issue.
Node's permission based permissions is enforced by adding the
--permissionflag when running Node.To get TailwindCSS up and running you also need to add:
The most problematic security issue in the above is (I think)
--allow-child-processwhich gives Tailwind's config/plugins more or less full OS access. Given the error message I get, I suspect this is due to how you loadlightningcss.