OptionalautoSideEffectsFalse?: booleanOptionalbundledWorkspaceDeps?: MaybeArray<string | RegExp>workspace dependencies that are bundled with the library, and as such shouldn't present in the final package.json
OptionalchunkFileName?: stringthe modifiable part of the chunk file name
there will be a prefix of chunks/[format]/ and a suffix of .js
OptionalcopyPackageFiles?: string[]files to copy from the package root directory to the build directory
OptionalcopyRootFiles?: string[]files to copy from the workspace root directory to the build directory
Optionalfinalize?: (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)
OptionalfinalizePackageJson?: (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)
OptionalinsertTypesEntry?: 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
OptionalpackageRoot?: stringpackage root, will be passed to vite's root option
OptionalpreparePackageJson?: (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)
OptionalrootFieldsToCopy?: string[]OptionaltypesEntryRoot?: 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: falseto generated package.json-s