For standalone sharing of projects, it's convenient to be able to package Leopard's library files right in the same folder as generated Leopard project source. This enables that use case by respecting leopardJSURL and leopardCSSURL values which are neither external (e.g. https://unpkg.com/...") nor absolute/root-relative (e.g. /leopard.min.css). If such a relative path is provided, e.g. leopard.min.css or lib/leopard.min.js, toLeopard will automatically supply the appropriate ./ or ../ prefix when importing the path in generated source.
Manually tested with custom local paths leopard.min.js and foo%20bar%20baz/leopard.min.js and snapshot-tested with the default unpkg values.
This is a standalone change which doesn't support any other PRs.
For standalone sharing of projects, it's convenient to be able to package Leopard's library files right in the same folder as generated Leopard project source. This enables that use case by respecting
leopardJSURLandleopardCSSURLvalues which are neither external (e.g.https://unpkg.com/...") nor absolute/root-relative (e.g./leopard.min.css). If such a relative path is provided, e.g.leopard.min.cssorlib/leopard.min.js, toLeopard will automatically supply the appropriate./or../prefix when importing the path in generated source.Manually tested with custom local paths
leopard.min.jsandfoo%20bar%20baz/leopard.min.jsand snapshot-tested with the default unpkg values.This is a standalone change which doesn't support any other PRs.