@bobfrankston/npmglobalize 1.0.231 → 1.0.232
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.
- package/cli.js +8 -5
- package/package.json +1 -1
package/cli.js
CHANGED
|
@@ -136,11 +136,14 @@ Other Options:
|
|
|
136
136
|
migration to-do list and exits. Writes nothing.
|
|
137
137
|
-tsfix, -ts7-fix
|
|
138
138
|
One-off utility, not the main flow: apply the TS7 tsconfig
|
|
139
|
-
migration to this package and its file: deps,
|
|
140
|
-
|
|
141
|
-
|
|
142
|
-
|
|
143
|
-
|
|
139
|
+
migration to this package and its file: deps, type-check
|
|
140
|
+
each with tsc --noEmit, add the extension NodeNext requires
|
|
141
|
+
on relative imports tsc flags ("./a" -> "./a.js", a noEmit
|
|
142
|
+
project gets ".ts"), and exit. tsconfig files and flagged
|
|
143
|
+
imports change — no emit, no commit, no push, no publish.
|
|
144
|
+
Whatever still fails to type-check is listed. The release
|
|
145
|
+
flow does the same on a TS7 build error; use this for an
|
|
146
|
+
in-place fix of a local directory: npmglobalize <path> -tsfix
|
|
144
147
|
-show Show package.json dependency changes
|
|
145
148
|
-package, -pkg Update package.json scripts to use npmglobalize
|
|
146
149
|
-h, -help Show this help
|