Include subdirectories in published npm JS package

[lourd]

Updates the files globs in package.json to include subdirectories in order to also include the flexbuffers directory in the published npm package.

Updates .gitignore to include the tsc-generated JS files.

Fixes #6849.

[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.

[lourd]

@googlebot I signed it!

[aardappel]

Thanks, @bjornharrtell can you check?

[bjornharrtell]

Lgtm

[aardappel]

Thanks :)

[lourd]

Thanks y'all!

When do you think a new version of the npm package will be published?

[aardappel]

Just tried to npm publish after changing the version in package.json to 2.0.4 (it was 2.0.3), but it ends with npm ERR! 404 'flatbuffers@2.0.4' is not in the npm registry. which.. confuses me.

[lourd]

Perhaps npm login again, get a fresh token? Based off npm/cli#1637 (comment))

[aardappel]

@lourd thanks, that was it. I'm not an npm user outside of making these releases :) Surprised they think the above is an adequate error for not being logged in.

It's on https://www.npmjs.com/package/flatbuffers and 2.0.4 has 95 files instead of the 50 of 2.0.3, which must mean.. things have improved :)