actions/ts-ci
2
0
Fork 0
mirror of https://github.com/garronej/ts-ci.git synced 2025-11-30 21:43:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge branch 'main' of https://github.com/garronej/ts-ci into main

Browse source
This commit is contained in:
garronej 2022-01-19 00:36:45 +01:00
commit 7593491937
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -10,7 +10,7 @@
`ts-ci` is a project starter like [TSDX](https://github.com/formium/tsdx) or [typescript-starter](https://github.com/bitjson/typescript-starter) but (arguably) better because: `ts-ci` is a project starter like [TSDX](https://github.com/formium/tsdx) or [typescript-starter](https://github.com/bitjson/typescript-starter) but (arguably) better because:
- It's not a CLI tool, the automation happens with Github Actions. - It's not a CLI tool, the automation happens with Github Actions.
Update your `package.json` version number, push. Voila, your new version is published on NPM. Update your `package.json` version number, push. Voila, your new version is published on NPM.
- It doesn't bundle your library into a single file so users can cherry-pick what they want to import from your lib. - It doesn't bundle your library into a single file so users can cherry-pick what they want to import from your lib, your modules will be tree shakable.
E.g: `import { aSpecificFunction } from "your-module/aSpecificFile"` E.g: `import { aSpecificFunction } from "your-module/aSpecificFile"`
<p align="center"> <p align="center">

2
README.template.md
View file

@ -31,7 +31,7 @@ $ npm install --save #{REPO_NAME}#
``` ```
```typescript ```typescript
import { myFunction, myObject } from "update_ts_ci"; import { myFunction, myObject } from "#{REPO_NAME}#";
``` ```
Specific imports: Specific imports: