@elemaudio/plugin-renderer - npm Package Compare versions

Comparing version 1.0.17 to 1.0.18

package.json

 {
   "name": "@elemaudio/plugin-renderer",
-  "version": "1.0.17",
+  "version": "1.0.18",
   "type": "module",
@@ -40,3 +40,3 @@ "description": "Official package for rendering Elementary Audio applications in the Plugin Dev Kit",
   },
-  "gitHead": "c8d2374a413f80bf5c14f26af4d05fce5eeee6c8"
+  "gitHead": "d9a7dd1cdc02bfd6e0693077a3dbcbbf1ca41e54"
 }

README.md

@@ -326,3 +326,5 @@ # @elemaudio/plugin-renderer
 Typically, you will want to prepare your web assets for production the same way you would in preparation for
-hosting on a static web server (i.e. bundling and minification). Once you've done that, point `elem-export` to
+hosting on a static web server (i.e. bundling and minification). This step is important; bundled assets within
+the exported plugin will be loaded from relative file URLs. If your assets reference each other with absolute
+paths, the exported plugin likely will fail to load. Now, once you've done that, point `elem-export` to
 the directory where your prepared assets are with the `-o` flag, and to your `manifest.json` file, which here is
@@ -329,0 +331,0 @@ equivalent to the `elementary.config.json` discussed in the above configuration section.

scripts/export.js

@@ -177,3 +177,3 @@ #!/usr/bin/env node
     // display in their plugin list
-    await fs.move(path.resolve(vst3Dest, 'Contents/x86_64-win/ElementaryDevKit'), path.resolve(vst3Dest, `Contents/x86_64-win/${manifestData.displayName}`), {overwrite: true});
+    await fs.move(path.resolve(vst3Dest, 'Contents/x86_64-win/ElementaryDevKit.vst3'), path.resolve(vst3Dest, `Contents/x86_64-win/${manifestData.displayName}.vst3`), {overwrite: true});
 
@@ -180,0 +180,0 @@ // Now we have to copy the assets

No alert changes

Improved metrics

Total package byte prevSize

23604439

Number of lines in readme file

337

increased by0.6%

No dependency changes