-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Shebang missing in dist/cli.mjs in published package #120
Comments
Related privatenumber/pkgroll#10. I did generate the last version on a Windows machine… perhaps the hashbang isn’t included when built on that OS as a weird edge case. I’ll look into publishing a fixed version soon. |
Thank you for the info and for looking into this. |
Sorry for the delay, I'll release a new version really soon (hopefully tomorrow or the day after). Google introduced icons into the API without distinguishing them as unique 😔 That has broken the parser for the time being, but I have a fix half done. |
Released in |
That's great. Thank you very much. 👍 |
Describe the bug
The file dist/cli.mjs in the published package does not contain a shebang line (
#!/usr/bin/env node
). This causes thenpx gfm …
command to fail with the following error:I cloned this project locally, ran
npm install
and after building, the dist dist/cli.mjs included the shebang:That’s odd. Maybe something has gone wrong while building the published version. This issue is probably Linux/macOS only (because without a shebang, the file is interpreted as a shell script instead of JS, which causes this syntax parsing error).
Steps to Reproduce
npm install google-font-metadata
in a Node.js project.npx gfm
Expected behavior
The
npx gfm …
command should run without an error.Version
5.0.1
OS
Linux
Browser
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: