redis-js icon indicating copy to clipboard operation
redis-js copied to clipboard

build(deps-dev): bump wrangler from 2.21.1 to 3.63.1 in /examples/cloudflare-workers

Open dependabot[bot] opened this issue 7 months ago • 0 comments

Bumps wrangler from 2.21.1 to 3.63.1.

Release notes

Sourced from wrangler's releases.

[email protected]

Patch Changes

  • #6192 b879ce4 Thanks @​petebacondarwin! - fix: do not report D1 user errors to Sentry

  • #6150 d993409 Thanks @​CarmenPopoviciu! - fix: Fix pages dev watch mode [_worker.js]

    The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "_worker.js" file, but not for changes in any of its imported dependencies. This means that given the following "_worker.js" file

    import { graham } from "./graham-the-dog";
    export default {
    	fetch(request, env) {
    		return new Response(graham)
    	}
    }
    

    pages dev will reload for any changes in the _worker.js file itself, but not for any changes in graham-the-dog.js, which is its dependency.

    Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.

    This commit fixes all the aforementioned issues.

[email protected]

Minor Changes

  • #6167 e048958 Thanks @​threepointone! - feature: alias modules in the worker

    Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might have imported node-fetch, which will probably never work in workerd. You can use the alias config to replace any of these imports with a module of your choice.

    Let's say you make a fetch-nolyfill.js

    export default fetch; // all this does is export the standard fetch function`
    

    You can then configure wrangler.toml like so:

    # ...
    [alias]
    "node-fetch": "./fetch-nolyfill"
    

    So any calls to import fetch from 'node-fetch'; will simply use our nolyfilled version.

    You can also pass aliases in the cli (for both dev and deploy). Like:

    npx wrangler dev --alias node-fetch:./fetch-nolyfill
    

... (truncated)

Changelog

Sourced from wrangler's changelog.

3.63.1

Patch Changes

  • #6192 b879ce4 Thanks @​petebacondarwin! - fix: do not report D1 user errors to Sentry

  • #6150 d993409 Thanks @​CarmenPopoviciu! - fix: Fix pages dev watch mode [_worker.js]

    The watch mode in pages dev for Advanced Mode projects is currently partially broken, as it only watches for changes in the "_worker.js" file, but not for changes in any of its imported dependencies. This means that given the following "_worker.js" file

    import { graham } from "./graham-the-dog";
    export default {
    	fetch(request, env) {
    		return new Response(graham)
    	}
    }
    

    pages dev will reload for any changes in the _worker.js file itself, but not for any changes in graham-the-dog.js, which is its dependency.

    Similarly, pages dev will not reload for any changes in non-JS module imports, such as wasm/html/binary module imports.

    This commit fixes all the aforementioned issues.

3.63.0

Minor Changes

  • #6167 e048958 Thanks @​threepointone! - feature: alias modules in the worker

    Sometimes, users want to replace modules with other modules. This commonly happens inside a third party dependency itself. As an example, a user might have imported node-fetch, which will probably never work in workerd. You can use the alias config to replace any of these imports with a module of your choice.

    Let's say you make a fetch-nolyfill.js

    export default fetch; // all this does is export the standard fetch function`
    

    You can then configure wrangler.toml like so:

    # ...
    [alias]
    "node-fetch": "./fetch-nolyfill"
    

    So any calls to import fetch from 'node-fetch'; will simply use our nolyfilled version.

    You can also pass aliases in the cli (for both dev and deploy). Like:

... (truncated)

Commits

Dependabot compatibility score

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @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[bot] avatar Jul 04 '24 23:07 dependabot[bot]