Gro extends package.json
with additional functionality.
Setting "public": true
in package.json
opts into
behavior designed for public open source projects:
gro_plugin_sveltekit_app
copiespackage.json
from your project root to your SvelteKit static directory at.well-known/package.json
duringvite build
, mapping it with the optionalwell_known_package_json
option.gro_plugin_sveltekit_app
outputs.well-known/src.json
using theexports
property ofpackage.json
duringvite build
, containing additional information about the source modules, mapping it with the optionalwell_known_src_json
option.- If you define a truthy value for the
well_known_src_files
option,gro_plugin_sveltekit_app
outputs.well-known/src/
by copying oversrc/
duringvite build
, filtered bywell_known_src_files
if it's a function. This is costly (usually more than doubling the final output size of the code files in bytes, not counting images and such), it slows the build because it copies your entire source tree (sorry to hard drives), and it exposes your source code the same as the built files.
⚠️ Setting"public": true
inpackage.json
exposes yourpackage.json
andsrc.json
metadata with your other built files by default! Further opting in withwell_known_src_files
exposes your actual source files. If your built files are public, that means these additional files are also public.