OptionalbundledOptionalcatalogsOptionaldependenciesOptionaldescriptionOptionaldevOptionalenginesOptionalfumanOptionaldistOnlyFields?: Record<string, unknown>any additional fields that will be shallowly merged into the resulting package.json. for more complex modifications than shallow merging, consider using build.config.js
Optionaljsr?: "skip" | "only"whether the package should be published to jsr (skip – it won't be published to jsr, only – it will only be published to jsr)
OptionalkeepScripts?: string[]by default @fuman/build strips all scripts, but you can keep some of them by passing their names here
Optionalnpm?: "skip" | "only"whether the package should be published to npm (skip – it won't be published to npm, only – it will only be published to npm)
OptionalownVersioning?: booleanwhether this package has its own versioning scheme, not managed by @fuman/build (be careful with this option! this might break cross-release semver compatibility)
Optionalprivate?: booleanwhether this package should not be published
Optionalstandalone?: booleanwhether this is a "standalone" package
standalone packages have a few differences from normal ones:
OptionalhomepageOptionalkeywordsOptionallicenseOptionalnameOptionaloptionalOptionalpackageOptionalpeerOptionalpnpmOptionalprivateOptionalrepositoryOptionalscriptsOptionaltypeOptionalversionOptionalworkspaces
fuman-specific package.json fields