feat: create npm package

[motiz88]

Closes #50.

• Basic structure of the package
• Publish under a temporary name (@motizilberman/dotslash)
  • Done using npm run build -- --version 0.5.7 --prerelease
• Test on all platforms
• Iterate on README and test the workflows described there
• Add docs
• Set up GitHub Action for publishing to npm on every release
• Add Flow and TypeScript definition files for convenience
• Decide on a final package name and publish a non-prerelease version
  • We can either ask npm nicely to free up dotslash - currently unavailable because of dot-slash, a package last published 10 years ago with 5 weekly downloads - or go with e.g. fb-dotslash (which I have reserved).
  • --> fb-dotslash
• Transfer package to Meta
  • --> added fb as a maintainer

Possible follow-up scope (definitely not in this PR):

• Add an optional postinstall script that replaces bin/dotslash with a symlink to the correct binary, thus making DotSlash'd tools start even faster in environments that respect postinstall scripts.

How to publish the package

cd node
npm ci
npm run lint
npm run build -- --tag v$RELEASED_DOTSLASH_VERSION # add --prerelease for testing
npm publish

[facebook-github-bot]

@facebook-github-bot has imported this pull request. If you are a Meta employee, you can view this in D79818880. (Because this pull request was imported automatically, there will not be any future comments.)

[motiz88]

Publishing as this is reasonably ready for review. In addition to reviewing, I'll need a maintainer to:

1. Make a decision on the package name.
2. If necessary, reach out to npm about freeing up the dotslash package name.
3. Action the package ownership transfer.

We should then update all references to @motizilberman/dotslash in this branch to whatever the final name is, merge, and run a release to make sure the automation is working end-to-end.

As a heads up, my team will start using this npm package (published manually as @motizilberman/dotslash) soon, e.g. in facebook/react-native#52930. We'd of course be more than happy to migrate to the "official" version of the package once that is published.

[motiz88]

cc @bigfootjon

[bigfootjon]

Make a decision on the package name.

lets do fb-dotslash

Action the package ownership transfer.

First step is to add fb to the package as an owner, ping me on workchat for the rest of the process

[facebook-github-bot]

This pull request was exported from Phabricator. Differential Revision: D79818880

[motiz88]

@bigfootjon: I've implemented the requested changes and fixed lint errors. I've also created a test branch and tag on facebook/dotslash to test the workflow, and it seems configuring the NPM auth token for fb is the last remaining piece (see logs).

[bigfootjon]

Review automatically exported from Phabricator review in Meta.

[motiz88]

I've now set up the npm token as a secret in this repo, updated my test branch and pushed a new test tag --> the package got published correctly:

• https://github.com/facebook/dotslash/actions/runs/17077907611/job/48424294428
• https://www.npmjs.com/package/fb-dotslash/v/0.0.0-test-release-motiz88-0-5-7-2-1755626867503

This should therefore be safe to merge, and will take effect from the next release of DotSlash.

[facebook-github-bot]

@motiz88 merged this pull request in 18deb7c.