@@ -40,14 +40,15 @@ const generateCustomElementsTypesOutput = async (
4040 `export declare const defineCustomElements: (opts?: any) => void;` ,
4141 `` ,
4242 `/**` ,
43- `* Used to manually set the base path where assets can be found.` ,
44- `* If the script is used as "module", it's recommended to use "import.meta.url",` ,
45- `* such as "setAssetPath(import.meta.url)". Other options include` ,
46- `* "setAssetPath(document.currentScript.src)", or using a bundler's replace plugin to` ,
47- `* dynamically set the path at build time, such as "setAssetPath(process.env.ASSET_PATH)".` ,
48- `* But do note that this configuration depends on how your script is bundled, or lack of` ,
49- `* bunding, and where your assets can be loaded from. Additionally custom bundling` ,
50- `* will have to ensure the static assets are copied to its build directory.` ,
43+ ` * Used to manually set the base path where assets can be found.` ,
44+ ` * If the script is used as "module", it's recommended to use "import.meta.url",` ,
45+ ` * such as "setAssetPath(import.meta.url)". Other options include` ,
46+ ` * "setAssetPath(document.currentScript.src)", or using a bundler's replace plugin to` ,
47+ ` * dynamically set the path at build time, such as "setAssetPath(process.env.ASSET_PATH)".` ,
48+ ` * But do note that this configuration depends on how your script is bundled, or lack of` ,
49+ ` * bunding, and where your assets can be loaded from. Additionally custom bundling` ,
50+ ` * will have to ensure the static assets are copied to its build directory.` ,
51+ ` */` ,
5152 `export declare const setAssetPath: (path: string) => void;` ,
5253 `` ,
5354 ] ;
0 commit comments