Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

fix(deps): update npm packages #112

Merged
merged 1 commit into from
Jan 27, 2025
Merged

fix(deps): update npm packages #112

merged 1 commit into from
Jan 27, 2025

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 19, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
hono (source) 4.6.14 -> 4.6.19 age adoption passing confidence
wrangler (source) 3.98.0 -> 3.105.1 age adoption passing confidence

Release Notes

honojs/hono (hono)

v4.6.19

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.18...v4.6.19

v4.6.18

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.17...v4.6.18

v4.6.17

Compare Source

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.16...v4.6.17

v4.6.16

Compare Source

What's Changed

Full Changelog: honojs/hono@v4.6.15...v4.6.16

v4.6.15

Compare Source

c.json() etc. throwing type error when the status is contentless code, e.g., 204

From this release, when c.json(), c.text(), or c.html() returns content, specifying a contentless status code such as 204 will now throw a type error.

CleanShot 2024-12-28 at 16 47 39@​2x

At first glance, this seems like a breaking change but not. It is not possible to return a contentless response with c.json() or c.text(). So, in that case, please use c.body().

app.get('/', (c) => {
  return c.body(null, 204)
})

What's Changed

New Contributors

Full Changelog: honojs/hono@v4.6.14...v4.6.15

cloudflare/workers-sdk (wrangler)

v3.105.1

Compare Source

Patch Changes

v3.105.0

Compare Source

Minor Changes

  • #​7466 e5ebdb1 Thanks @​Ltadrian! - feat: implement the wrangler cert upload command

    This command allows users to upload a mTLS certificate/private key or certificate-authority certificate chain.

    For uploading mTLS certificate, run:

    • wrangler cert upload mtls-certificate --cert cert.pem --key key.pem --name MY_CERT

    For uploading CA certificate chain, run:

    • wrangler cert upload certificate-authority --ca-cert server-ca.pem --name SERVER_CA
Patch Changes

v3.104.0

Compare Source

Minor Changes

  • #​7715 26fa9e8 Thanks @​penalosa! - Support service bindings from Pages projects to Workers in a single workerd instance. To try it out, pass multiple -c flags to Wrangler: i.e. wrangler pages dev -c wrangler.toml -c ../other-worker/wrangler.toml. The first -c flag must point to your Pages config file, and the rest should point to Workers that are bound to your Pages project.

  • #​7816 f6cc029 Thanks @​dario-piotrowicz! - add support for assets bindings to getPlatformProxy

    this change makes sure that that getPlatformProxy, when the input configuration
    file contains an assets field, correctly returns the appropriate asset binding proxy

    example:

    // wrangler.json
{
  "name": "my-worker",
  "assets": {
    "directory": "./public/",
    "binding": "ASSETS"
  },
  "vars": {
    "MY_VAR": "my-var"
  }
}
    import { getPlatformProxy } from "wrangler";

const { env, dispose } = await getPlatformProxy();

if (env.ASSETS) {
  const text = await (
    await env.ASSETS.fetch("http://0.0.0.0/file.txt")
  ).text();
  console.log(text); // logs the content of file.txt
}

await dispose();
Patch Changes

v3.103.2

Compare Source

Patch Changes

v3.103.1

Compare Source

Patch Changes

v3.103.0

Compare Source

Minor Changes

  • #​5086 8faf2c0 Thanks @​dario-piotrowicz! - add --strict-vars option to wrangler types

    add a new --strict-vars option to wrangler types that developers can (by setting the
    flag to false) use to disable the default strict/literal types generation for their variables

    opting out of strict variables can be useful when developers change often their vars values,
    even more so when multiple environments are involved

v3.102.0

Compare Source

Minor Changes
Patch Changes

v3.101.0

Compare Source

Minor Changes

  • #​7534 7c8ae1c Thanks @​cmackenzie1! - feat: Use OAuth flow to generate R2 tokens for Pipelines

  • #​7674 45d1d1e Thanks @​Ankcorn! - Add support for env files to wrangler secret bulk i.e. .dev.vars

    Run wrangler secret bulk .dev.vars to add the env file

    //.dev.vars
KEY=VALUE
KEY_2=VALUE

    This will upload the secrets KEY and KEY_2 to your worker

  • #​7442 e4716cc Thanks @​petebacondarwin! - feat: add support for redirecting Wrangler to a generated config when running deploy-related commands

    This new feature is designed for build tools and frameworks to provide a deploy-specific configuration,
    which Wrangler can use instead of user configuration when running deploy-related commands.
    It is not expected that developers of Workers will need to use this feature directly.

Affected commands

The commands that use this feature are:

  • wrangler deploy
  • wrangler dev
  • wrangler versions upload
  • wrangler versions deploy
  • wrangler pages deploy
  • wrangler pages build
  • wrangler pages build-env
Config redirect file

When running these commands, Wrangler will look up the directory tree from the current working directory for a file at the path .wrangler/deploy/config.json. This file must contain only a single JSON object of the form:

{ "configPath": "../../path/to/wrangler.json" }

When this file exists Wrangler will follow the configPath (relative to the .wrangler/deploy/config.json file) to find an alternative Wrangler configuration file to load and use as part of this command.

When this happens Wrangler will display a warning to the user to indicate that the configuration has been redirected to a different file than the user's configuration file.

Custom build tool example

A common approach that a build tool might choose to implement.

  • The user writes code that uses Cloudflare Workers resources, configured via a user wrangler.toml file.

    name = "my-worker"
main = "src/index.ts"
[[kv_namespaces]]
binding = "<BINDING_NAME1>"
id = "<NAMESPACE_ID1>"

    Note that this configuration points main at user code entry-point.

  • The user runs a custom build, which might read the wrangler.toml to find the entry-point:

    > my-tool build

  • This tool generates a dist directory that contains both compiled code and a new deployment configuration file, but also a .wrangler/deploy/config.json file that redirects Wrangler to this new deployment configuration file:

    - dist
  - index.js
	- wrangler.json
- .wrangler
  - deploy
	  - config.json

    The dist/wrangler.json will contain:

    {
  "name": "my-worker",
  "main": "./index.js",
  "kv_namespaces": [
    { "binding": "<BINDING_NAME1>", "id": "<NAMESPACE_ID1>" }
  ]
}

    And the .wrangler/deploy/config.json will contain:

    {
  "configPath": "../../dist/wrangler.json"
}

  • #​7685 9d2740a Thanks @​vicb! - allow overriding the unenv preset.

    By default wrangler uses the bundled unenv preset.

    Setting WRANGLER_UNENV_RESOLVE_PATHS allow to use another version of the preset.
    Those paths are used when resolving the unenv module identifiers to absolute paths.
    This can be used to test a development version.

  • #​7694 f3c2f69 Thanks @​joshthoward! - Default wrangler d1 export to --local rather than failing

Patch Changes

v3.100.0

Compare Source

Minor Changes

  • #​7604 6c2f173 Thanks @​CarmenPopoviciu! - feat: Capture Workers with static assets in the telemetry data

    We want to measure accurately what this number of Workers + Assets projects running in remote mode is, as this number will be a very helpful data point down the road, when more decisions around remote mode will have to be taken.

    These changes add this kind of insight to our telemetry data, by capturing whether the command running is in the context of a Workers + Assets project.

    N.B. With these changes in place we will be capturing the Workers + Assets context for all commands, not just wrangler dev --remote.

Patch Changes

  • #​7581 cac7fa6 Thanks @​vicb! - chore(wrangler): update unenv dependency version

    unenv now uses the workerd implementation on node:dns
    See the unjs/unenv#376

  • #​7625 d8fb032 Thanks @​vicb! - feat(wrangler): use unenv builtin dependency resolution

    Moving away from require.resolve() to handle unenv aliased packages.
    Using the unenv builtin resolution will allow us to drop the .cjs file from the preset
    and to override the base path so that we can test the dev version of the preset.

  • #​7533 755a27c Thanks @​danielgek! - Add warning about the browser rendering not available on local

  • #​7614 8abb43f Thanks @​vicb! - chore(wrangler): update unenv dependency version

    The updated unenv contains a fix for the module resolution,
    see unjs/unenv#378.
    That bug prevented us from using unenv module resolution,
    see #​7583.

  • Updated dependencies [b4e0af1]:

v3.99.0

Compare Source

Minor Changes

  • #​7425 8757579 Thanks @​CarmenPopoviciu! - feat: Make DX improvements in wrangler dev --remote

    Workers + Assets projects have, in certain situations, a relatively degraded wrangler dev --remote developer experience, as opposed to Workers proper projects. This is due to the fact that, for Workers + Assets, we need to make extra API calls to:

    1. check for asset files changes
    2. upload the changed assets, if any

    This commit improves the wrangler dev --remote DX for Workers + Assets, for use cases when the User Worker/assets change while the API calls for previous changes are still in flight. For such use cases, we have put an exit early strategy in place, that drops the event handler execution of the previous changes, in favour of the handler triggered by the new changes.

  • #​7537 086a6b8 Thanks @​WillTaylorDev! - Provide validation around assets.experimental_serve_directly

  • #​7568 2bbcb93 Thanks @​WillTaylorDev! - Warn users when using smart placement with Workers + Assets and serve_directly is set to false

Patch Changes

  • #​7521 48e7e10 Thanks @​emily-shen! - feat: add experimental_patchConfig()

    experimental_patchConfig() can add to a user's config file. It preserves comments if its a wrangler.jsonc. However, it is not suitable for wrangler.toml with comments as we cannot preserve comments on write.

  • Updated dependencies [1488e11, 7216835]:

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/npm-packages branch from 486eefc to bdec3be Compare December 28, 2024 10:20
@renovate renovate bot changed the title fix(deps): update dependency wrangler to v3.99.0 fix(deps): update npm packages Dec 28, 2024
@renovate renovate bot force-pushed the renovate/npm-packages branch 3 times, most recently from 3dec63f to c724605 Compare January 10, 2025 00:36
@renovate renovate bot force-pushed the renovate/npm-packages branch 6 times, most recently from bee470f to 838f0bd Compare January 18, 2025 10:13
@renovate renovate bot force-pushed the renovate/npm-packages branch 5 times, most recently from d6328d6 to 0336a20 Compare January 24, 2025 19:11
@renovate renovate bot force-pushed the renovate/npm-packages branch from 0336a20 to 1c0acb9 Compare January 26, 2025 10:43
@Lulalaby Lulalaby merged commit 53f66cd into main Jan 27, 2025
@Lulalaby Lulalaby deleted the renovate/npm-packages branch January 27, 2025 03:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@Lulalaby