Closed bombillazo closed 2 years ago
The issue is that I don't have a windows device to test on it will try to fix it
Hey @AhmedElywa ,I think I know what is happening.
Since the config file for Pal is called pal.js
, Yarn is trying to directly run the file instead of calling the pal cli installed.
I think a good convention would be to rename the pal.js
config file to something like .palrc.js
or pal.config.js
to avoid conflict
In the meantime I will use pal.json
file but I would prefer to have it as a js file eventually.
Given a package.json script like
"generate:pal": "pal g",
Running it via yarn or npm in Windows gives you the following error:
Running it directly on the terminal works as expected.