Open sbimochan opened 3 months ago
What version of Tailwind CSS are you using?
v3.3.3
What build tool (or framework if it abstracts the build tool) are you using?
webpack v5
What version of Node.js are you using?
v20
What browser are you using?
Chrome
What operating system are you using?
macOS
Describe your issue
After compiling, the css generated are different from macOS and Linux(maybe or could be of different according to machines) For e.g:
If we use classNames like top-1 and top-1\/2 In one machines (macOS) the output.css file contains:
top-1
top-1\/2
.nv-top-1 { top: 0.25rem; } .nv-top-1\/2 { top: 50%; }
and on some other place: it's opposite
.nv-top-1\/2 { top: 50%; } .nv-top-1 { top: 0.25rem; }
Maybe it's something with oxide compiler and system setting how to treat \ and number on ascending order.
If you upgrade to v3.4 do you still see this problem?
Yes
What version of Tailwind CSS are you using?
v3.3.3
What build tool (or framework if it abstracts the build tool) are you using?
webpack v5
What version of Node.js are you using?
v20
What browser are you using?
Chrome
What operating system are you using?
macOS
Describe your issue
After compiling, the css generated are different from macOS and Linux(maybe or could be of different according to machines) For e.g:
If we use classNames like
top-1
andtop-1\/2
In one machines (macOS) the output.css file contains:and on some other place: it's opposite
Maybe it's something with oxide compiler and system setting how to treat \ and number on ascending order.