Closed mikepuglisi closed 2 years ago
I found the solution / workaround on your discord which was posted by another user.
@bombillazo stated: "turns out it was due to a naming conflict in the pal.js file on the root folder. Yarn tris to run that file as the command instead of using the install pal.js cli my workaround is to change it to pal.json so yarn does not try to run that file"
Once I renamed pal.js to pal.json, I was able to run the "yarn generate" command.
I followed the "Getting Started" and received the following error when I run the "generate" npm script
It isn't clear to me if "pal" is supposed to be a globally available command that maps to an application via my system PATH.
Note that "pal" is not available globally, but this may be unrelated: