Add #!/usr/bin/env node to the top of the cli/index.ts

[dmitryrn]

That will make executing via npx working. (#36). tsc will build it without error.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[dmitryrn]

@googlebot I signed it!

[ryanmcdermott]

Thanks!

[jasco]

It appears as if npm release 0.2.4, which should includes this patch, didn't get rebuilt before distribution? The shebang is missing from the build/src/cli/index.js file in the npm install. If I manually build it locally, the shebang does appear in the header as expected.

(Looking at the diff after rebuild it looks like at least the outputFormat option was missing from the build as well.)

[ryanmcdermott]

It's really strange, I could swear I re-built it. In my rather inadequate defense, I must say I'm not a Node expert actually. I'm not a self-professed member of the wider JS/TS community anymore.

For what it's worth, I ran npm link locally to verify that it worked globally and checked the build dates via ls -al and it looks correct in version 0.2.5. Let me know if this fixes it!

Sorry for the back and forth, thanks for all your help!

[jasco]

Version 0.2.5 does work as expected for me now. Thanks.