quotes in 'shadow'.props.*.css build #281
-
Hello, this doesn't look healthy and those ':host' {
--blue-0: #e7f5ff;
--blue-1: #d0ebff;
--blue-2: #a5d8ff;
...
} this couldn't have gone unnoticed, could it? 😁 |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
although I liked the number of layers in "Git Bash for Windows inside the VS Code terminal" it appears to be a general Windows issue: good old cmd.exe or bash.exe -- the resulting filenames and single quoted :host are the same. Somehow this script call I know next to nothing about writing code for Node specifically, but my bet would be that somewhere here an "OS check" would be in order or some sanitising of the single quotes passed as arguments. 🤷♂️ |
Beta Was this translation helpful? Give feedback.
-
using double quotes fixes the issue under Windows' "gen:op": "cd build && node props.js \"\" true",
"gen:nowhere": "cd build && node props \"\" false",
"gen:shadowdom": "cd build && node props \"\" false \":host\" \"shadow\"",
"gen:prefixed": "cd build && node props.js \"op\" true", I currently can't test on Linux and I only have access to organic apples. It apparently doesn't build properly under PowerShell at all. It's handling of command line arguments is very bizarre, and shadow {
--false-blue-0: #e7f5ff;
--false-blue-1: #d0ebff;
--false-blue-2: #a5d8ff;
--false-blue-3: #74c0fc;
...
} the newly created token files look ok to me. |
Beta Was this translation helpful? Give feedback.
using double quotes fixes the issue under Windows'
cmd.exe
, where'
is not a valid command line string delimiter.I currently can't test on Linux and I only have access to organic apples.
It apparently doesn't build properly under PowerShell at all. It's handling of command line arguments is very bizarre, and
both
node .\props.js "" false ":host" "shadow"
(double ")and
node .\props.js '' false ':host' 'shadow'
(single ')don't create any
shadow.*.css' at all …