Bump @cloudflare/kv-asset-handler from 0.1.3 to 0.2.0 in /workers-site

[dependabot]

Bumps @cloudflare/kv-asset-handler from 0.1.3 to 0.2.0.

Release notes

Sourced from @​cloudflare/kv-asset-handler's releases.

0.2.0

• Features

  • Allow changing pathIsEncoded through options - JackPriceBurns, pull/243

    When using mapRequestToAsset, it encodes the URL / key and will never check the KV store for the decoded key.

    This adds the ability to set pathIsEncoded to true, which will decode the URL before getting it from the KV.

  • Support ES Modules. - threepointone, pull/261

    This PR provides a possible solution for getting Workers Sites working with ES Module workers. This approach is not as invasive as other approaches, so isn't as risky either.

    Usage:

    import manifestJSON from "__STATIC_CONTENT_MANIFEST";
    const manifest = JSON.parse(manifestJSON);
    export default {
    fetch(request, env, ctx) {
    return await getAssetFromKV(
    {
    request,
    waitUntil(promise) {
    return ctx.waitUntil(promise);
    },
    },
    {
    ASSET_NAMESPACE: env.ASSET_NAMESPACE,
    ASSET_MANIFEST: manifest,
    }
    );
    // ...
    },
    };

• Fixes

  • fix: default ASSET_MANIFEST to empty object - [Cherry], [pull/254]

    As per discussion in Discord and the repo at [https://github.com/Erisa-bits/getassetfromkv-undefined-error], allowing ASSET_MANIFEST to be optional got lost somewhere along the years and errors when attempted to be used without it. This PR restores this functionality by setting it to an empty object (instead of undefined), which allows fall-through to the standard mapRequestToAsset function.

... (truncated)

Changelog

Sourced from @​cloudflare/kv-asset-handler's changelog.

0.2.0

• Features

  • Allow changing pathIsEncoded through options - JackPriceBurns, pull/243

    When using mapRequestToAsset, it encodes the URL / key and will never check the KV store for the decoded key.

    This adds the ability to set pathIsEncoded to true, which will decode the URL before getting it from the KV.

  • Support ES Modules. - threepointone, pull/261

    This PR provides a possible solution for getting Workers Sites working with ES Module workers. This approach is not as invasive as other approaches, so isn't as risky either.

    Usage:

    import manifestJSON from "__STATIC_CONTENT_MANIFEST";
    const manifest = JSON.parse(manifestJSON);
    export default {
    fetch(request, env, ctx) {
    return await getAssetFromKV(
    {
    request,
    waitUntil(promise) {
    return ctx.waitUntil(promise);
    },
    },
    {
    ASSET_NAMESPACE: env.ASSET_NAMESPACE,
    ASSET_MANIFEST: manifest,
    }
    );
    // ...
    },
    };

• Fixes

  • fix: default ASSET_MANIFEST to empty object - [Cherry], [pull/254]

    As per discussion in Discord and the repo at [https://github.com/Erisa-bits/getassetfromkv-undefined-error], allowing ASSET_MANIFEST to be optional got lost somewhere along the years and errors when attempted to be used without it. This PR restores this functionality by setting it to an empty object (instead of undefined), which allows fall-through to the standard mapRequestToAsset function.

... (truncated)

Commits

• ff8d3dc Merge pull request #266 from cloudflare/threepointone-patch-1
• c5d735b updating version in package.json to 0.2.0
• e299347 Merge pull request #263 from cloudflare/0.2.0
• 953a8c9 Merge pull request #265 from cloudflare/env-static-content
• 129d678 s/env.ASSET_NAMESPACE/env.__STATIC_CONTENT
• f24b3ca Merge pull request #264 from cloudflare/cass/update-docs-es-modules
• 6c4cd81 Update README to reflect support for ES Modules
• ae7f633 fixup! 0.2.0
• 450a45b 0.2.0
• fd27ccf Merge pull request #261 from cloudflare/es-worker-compat
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by threepointone, a new releaser for @​cloudflare/kv-asset-handler since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #181.