toolkit/scripts/create-package

#!/usr/bin/env bash

set -eo pipefail

name=$1

if [[ -z "$name" ]]; then
  >&2 echo "Usage: npm run new-package [name]"
  exit 1
fi

npx lerna create @actions/$name
cp packages/core/tsconfig.json packages/$name/tsconfig.json
Simplify package creation 2019-04-22 15:54:05 +00:00			`#!/usr/bin/env bash`

			`set -eo pipefail`

			`name=$1`

			`if [[ -z "$name" ]]; then`
			`>&2 echo "Usage: npm run new-package [name]"`
			`exit 1`
			`fi`

Move @actions/http-client into the toolkit (#1062) 💡 See https://github.com/actions/toolkit/pull/1064 for a better diff! https://github.com/actions/toolkit contains a variety of packages used for building actions. https://github.com/actions/http-client is one such package, but lives outside of the toolkit. Moving it inside of the toolkit will improve discoverability and reduce the number of repos we have to keep track of for maintenance tasks (such as github/c2c-actions-service#2937). I checked with @bryanmacfarlane on the historical decision here. Apparently it was just inertia from before we released the toolkit as multiple packages. The benefits here are: - Have one fewer repo to keep track of - Signal that this is an HTTP client meant for building actions, not for general use. ## Notes - `@actions/http-client` will continue to be released as its own package. - Bumping the package version to 2.0.0. Since we're compiling in strict mode now, there are some breaking changes to the exported types. This is an improvement because the null-unsafe version of`http-client` is currently breaking the safety of null-safe consumers. - I'm not updating the other packages to use the new version in this PR. I plan to do that in a follow-up. We'll hold off on publishing `http-client` v2 to NPM until that's done just in case other changes shake out of it. 2022-05-03 15:10:13 +00:00			`npx lerna create @actions/$name`
			`cp packages/core/tsconfig.json packages/$name/tsconfig.json`