Optional
autoSideEffectsFalse?: booleanOptional
bundledWorkspaceDeps?: MaybeArray<string | RegExp>workspace dependencies that are bundled with the library, and as such shouldn't present in the final package.json
Optional
chunkFileName?: stringthe modifiable part of the chunk file name
there will be a prefix of chunks/[format]/
and a suffix of .js
Optional
copyPackageFiles?: string[]files to copy from the package root directory to the build directory
Optional
copyRootFiles?: string[]files to copy from the workspace root directory to the build directory
Optional
finalize?: (ctx: BuildHookContext) => MaybePromise<void>hook to run after the build is done, time to do any final modifications to the package contents (note: this hook is run before package-level hooks)
Optional
finalizePackageJson?: (ctx: BuildHookContext) => MaybePromise<void>hook to run after the package.json file is finalized, right before it is written to disk you can modify the .packageJson property of the context (note: this hook is run before package-level hooks)
Optional
insertTypesEntry?: booleanwhen using with vite-plugin-dts
, use this flag instead of
their insertTypesEntry
option to insert the types entry,
as their implementation doesn't always yield the correct result
Optional
packageRoot?: stringpackage root, will be passed to vite's root
option
Optional
preparePackageJson?: (ctx: BuildHookContext) => voidhook to run before anything is done to the package.json file you can modify the .packageJson property of the context
this hook is called before vite build has started,
and as such .outDir
is not available yet
(note: this hook is run before package-level hooks)
Optional
rootFieldsToCopy?: string[]Optional
typesEntryRoot?: stringwhen using with vite-plugin-dts
, this value should match entryRoot
value passed to the vite-plugin-dts
plugin
when true, will automatically add
sideEffects: false
to generated package.json-s