You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: documentation/docs/30-advanced/70-packaging.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -219,7 +219,7 @@ You should think carefully about whether or not the changes you make to your pac
219
219
220
220
-`-w`/`--watch` — watch files in `src/lib` for changes and rebuild the package
221
221
-`-i`/`--input` — the input directory which contains all the files of the package. Defaults to `src/lib`
222
-
-`-o`/`--o` — the output directory where the processed files are written to. Your `package.json`'s `exports` should point to files inside there, and the `files` array should include that folder. Defaults to `dist`
222
+
-`-o`/`--output` — the output directory where the processed files are written to. Your `package.json`'s `exports` should point to files inside there, and the `files` array should include that folder. Defaults to `dist`
223
223
-`-t`/`--types` — whether or not to create type definitions (`d.ts` files). We strongly recommend doing this as it fosters ecosystem library quality. Defaults to `true`
224
224
-`--tsconfig` - the path to a tsconfig or jsconfig. When not provided, searches for the next upper tsconfig/jsconfig in the workspace path.
0 commit comments