@tsmodule/tsmodule 41.38.0 → 41.39.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/README.md +4 -4
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -107,11 +107,11 @@ With `-b, --bundle` mode, all entry points are compiled "in-place" and runtime N
107
107
 
108
108
  TSModule itself builds with `-b, --bundle` flag, and requires only three runtime NPM dependencies:
109
109
 
110
- 1. `esbuild`, which does the heavy lifting for the build process, does not allow itself to be bundled
110
+ 1. `esbuild`, which does the heavy lifting for the build process, does not allow itself to be bundled;
111
111
  2. `typescript`, so TSModule can use the built `tsc` binary to generate `.d.ts`
112
- type declarations during builds
113
- 3. `pkg`, for building binaries with `build --binary` (which implies `--bundle`
114
- and `--standalone src/bin.ts`).
112
+ type declarations during builds; and
113
+ 3. `pkg`, for building binaries with `build --binary` (a specific standalone
114
+ bundle mode).
115
115
 
116
116
  <sub>Note: Bundling every entry point in place may not be what you want, i.e. if you
117
117
  only have a single entrypoint. In these cases, `tsmodule build -b src/index.ts`
package/package.json CHANGED
@@ -2,7 +2,7 @@
2
2
  "name": "@tsmodule/tsmodule",
3
3
  "platform": "node",
4
4
  "type": "module",
5
- "version": "41.38.0",
5
+ "version": "41.39.0",
6
6
  "repository": "tsmodule/tsmodule",
7
7
  "description": "Create standardized TypeScript ESM packages for Node or browser.",
8
8
  "license": "MIT",