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.

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

chore(deps): update all non-major dependencies #2354

Merged
merged 2 commits into from Jun 2, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 2, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@changesets/cli (source) 2.25.0 -> 2.26.1 age adoption passing confidence
@types/node (source) 18.7.18 -> 18.16.16 age adoption passing confidence
@types/ramda (source) 0.28.22 -> 0.29.2 age adoption passing confidence
@types/react (source) 18.2.6 -> 18.2.8 age adoption passing confidence
apollo-server 3.11.1 -> 3.12.0 age adoption passing confidence
apollo-server-express 3.11.1 -> 3.12.0 age adoption passing confidence
dataloader 2.1.0 -> 2.2.2 age adoption passing confidence
next (source) 13.4.3 -> 13.4.4 age adoption passing confidence
ramda (source) ^0.28.0 -> ^0.29.0 age adoption passing confidence
wrangler 2.1.9 -> 2.20.0 age adoption passing confidence

Release Notes

changesets/changesets

v2.26.1

Compare Source

Patch Changes
  • #​1115 feddc88 Thanks @​Andarist! - Call pnpm publish directly from the directory of the published package. This allows pnpm to correctly handle configured publishConfig.directory.

v2.26.0

Compare Source

Minor Changes
  • #​1033 521205d Thanks @​Andarist! - A new config-level changedFilePatterns option has been added. You can configure it with an array of glob patterns like here:

    // .changeset/config.json
    {
      "changedFilePatterns": ["src/**"]
    }

    Files that do not match the configured pattern won't contribute to the "changed" status of the package to which they belong. This both affects changesets add and changeset status.

Patch Changes

v2.25.2

Compare Source

Patch Changes

v2.25.1

Compare Source

Patch Changes
  • #​997 4d4d67b Thanks @​JakeGinnivan! - Add error message when running changesets in a repo with workspaces configured but no packages yet

  • #​985 8d0115e Thanks @​mino01x! - Fixed an issue with private packages with versions being included in the CLI prompt despite the privatePackages.version: false setting.

apollographql/apollo-server (apollo-server)

v3.12.0

Compare Source

apollographql/apollo-server (apollo-server-express)

v3.12.0

Compare Source

graphql/dataloader

v2.2.2

Compare Source

Patch Changes

v2.2.1

Compare Source

Patch Changes

v2.2.0

Compare Source

Minor Changes
Patch Changes
  • #​318 588a8b6 Thanks @​boopathi! - Fix the propagation of sync throws in the batch function to the loader function instead of crashing the process wtih an uncaught exception.
  • #​321 3cd3a43 Thanks @​thekevinbrown! - Resolves an issue where the maxBatchSize parameter wouldn't be fully used on each batch sent to the backend loader.
vercel/next.js

v13.4.4

Compare Source

Core Changes
  • test(turbopack): script to sync latest test lists: #​50008
  • Pages Module Transition: #​49962
  • Server Actions: Fix member expr in closure captured values: #​50020
  • Error in next export when serverActions is enabled: #​50039
  • [turbopack]: Update renamed SubpathValue: #​49636
  • Fix default metadata is missing in root not-found: #​50044
  • Always defer close tags to be the suffix of body stream: #​50056
  • Fix types of cookies(): #​50052
  • Fix client references extraction of CJS exports analysis: #​50059
  • Add x-forwarded-* headers to turbopack renders: #​50012
  • Remove node-sass from peerDependencies: #​50065
  • Add optional generic parameter to NextResponse: #​47526
  • feat(turbopack): initial sass-loader support: #​49882
  • update test snapshots: #​50159
  • [create-next-app]: respecting the user's init.defaultBranch git con…: #​49960
  • Update swc_core to v0.76.18: #​50137
  • Fix navigating on not-found: #​50047
  • Fix env variables set in next.config.js: #​50179
  • Add warning for edge with force-static: #​50182
  • fix: add missing draftMode type to GetServerSidePropsContext: #​50184
  • Fix react fetch deduping without next cache: #​50187
  • Fix pages react alias: #​50128
  • Add the node condition to import resolution: #​50007
  • test(turbopack): run next.js integration tests with denylist: #​50172
  • Move debugging variable into useEffect: #​50210
  • refactor webpack loaders: #​49535
  • Fix static workers distributing: #​50194
  • Ensure NEXT_DYNAMIC_NO_SSR_CODE has a unique name: #​50219
  • fix: Added blockfrost-js, lucid-cardano & mongoose package to srvExtPackages to prevent issue #​49783 from happening.: #​49938
  • change static path to /_next/static/media: #​50207
  • Add special route types to the link type declaration: #​50066
  • fix: NODE_OPTIONS='--inspect' in next dev for debugging: #​48019
  • enable more test cases for turbopack: #​50154
  • feat(next-swc): Implement CJS optimizer: #​49972
  • Fix alias for react-dom/server: #​50238
  • Revert "feat(next-swc): Implement CJS optimizer": #​50247
  • Fix free port handling: #​50248
  • feat(next-swc): Add CJS optimizer again: #​50249
  • Fix edge case in the CJS optimizer: #​50258
  • Remove static analysis of process.env: #​50260
  • Update next start listening to behave consistently: #​50293
  • Update server invoke-request: #​50296
  • Update unstable_cache key to include args: #​50301
  • Add root detection utils: #​50305
  • fix sass handling after refactoring: #​50259
  • Alias next/server for edge runtime: #​50268
  • [turbopack]: Serve _devMiddlewareManifest.json from router: #​50241
  • Fix catch-all edge app route: #​50313
  • land: Include charset=utf-8 with x-component Content-Type header: #​50314
  • do not apply sass loader on existing loaders: #​50308
  • Add missing react-dom/client alias: #​50324
  • Fix missing error when using Actions on the client layer without enabling the feature flag: #​50257
  • remove allowlist, only use denylist, enable newly passing tests: #​50325
  • Fix SWC loader options for files outside of RSC layers: #​50341
Documentation Changes
  • Update app-static-to-dynamic-error.md: #​50085
  • Update invalid-new-link-with-extra-anchor.md: #​50036
Example Changes
  • fix: use node copyFile for cross-platform support: #​48740
  • Clerk example updates: #​50021
  • Fix TypeScript error in with-mongodb example: #​50094
  • Use correct casing in filenames: #​50223
Misc Changes
Credits

Huge thanks to @​kwonoj, @​wyattjoh, @​shuding, @​huozhi, @​jridgewell, @​ijjk, @​karlhorky, @​lycuid, @​MarkAtOmniux, @​darshkpatel, @​johnta0, @​kdy1, @​sokra, @​timneutkens, @​devagrawal09, @​ibrahemid, @​styfle, @​JesseKoldewijn, @​padmaia, @​Cow258, @​javivelasco, and @​05lazy for helping!

ramda/ramda

v0.29.0

Compare Source

Added

🆕 addIndexRight
🆕 isNotNil
🆕 swap
🆕 dropRepeatsBy

Removed
Deprecated
Changes

⚠️ propEq/pathEq parameter order

  • Documentation improvements
  • Transducer updates
  • Some support for types
  • Many more!

Thank you to everyone who contributed to this release!

cloudflare/workers-sdk

v2.20.0

Compare Source

Minor Changes
  • #​3095 133c0423 Thanks @​zebp! - feat: add support for placement in wrangler config

    Allows a placement object in the wrangler config with a mode of off or smart to configure Smart placement. Enabling Smart Placement can be done in your wrangler.toml like:

    [placement]
    mode = "smart"
  • #​3140 5fd080c8 Thanks @​penalosa! - feat: Support sourcemaps in DevTools

    Intercept requests from DevTools in Wrangler to inject sourcemaps and enable folders in the Sources Panel of DevTools. When errors are thrown in your Worker, DevTools should now show your source file in the Sources panel, rather than Wrangler's bundled output.

Patch Changes

v2.19.0

Compare Source

Minor Changes

v2.18.0

Compare Source

Minor Changes
  • #​3098 8818f551 Thanks @​mrbbot! - fix: improve Workers Sites asset upload reliability

    • Wrangler no longer buffers all assets into memory before uploading. This should prevent out-of-memory errors when publishing sites with many large files.
    • Wrangler now limits the number of in-flight asset upload requests to 5, fixing the Too many bulk operations already in progress error.
    • Wrangler now correctly logs upload progress. Previously, the reported percentage was per upload request group, not across all assets.
    • Wrangler no longer logs all assets to the console by default. Instead, it will just log the first 100. The rest can be shown by setting the WRANGLER_LOG=debug environment variable. A splash of colour has also been added.

v2.17.0

Compare Source

Minor Changes
  • #​3004 6d5000a7 Thanks @​rozenmd! - feat: teach wrangler docs to use algolia search index

    This PR lets you search Cloudflare's entire docs via wrangler docs [search term here].

    By default, if the search fails to find what you're looking for, you'll get an error like this:

    ✘ [ERROR] Could not find docs for: <search term goes here>. Please try again with another search term.
    

    If you provide the --yes or -y flag, wrangler will open the docs to https://developers.cloudflare.com/workers/wrangler/commands/, even if the search fails.

v2.16.0

Compare Source

Minor Changes
  • #​3058 1bd50f56 Thanks @​mrbbot! - chore: upgrade miniflare@3 to 3.0.0-next.13

    Notably, this adds native support for Windows to wrangler dev --experimental-local, logging for incoming requests, and support for a bunch of newer R2 features.

Patch Changes
  • #​3058 1bd50f56 Thanks @​mrbbot! - fix: disable persistence without --persist in --experimental-local

    This ensures --experimental-local doesn't persist data on the file-system, unless the --persist flag is set.
    Data is still always persisted between reloads.

  • #​3055 5f48c405 Thanks @​rozenmd! - fix: Teach D1 commands to read auth configuration from wrangler.toml

    This PR fixes a bug in how D1 handles a user's accounts. We've updated the D1 commands to read from config (typically via wrangler.toml) before trying to run commands. This means if an account_id is defined in config, we'll use that instead of erroring out when there are multiple accounts to pick from.

    Fixes #​3046

  • #​3058 1bd50f56 Thanks @​mrbbot! - fix: disable route validation when using --experimental-local

    This ensures wrangler dev --experimental-local doesn't require a login or an internet connection if a route is configured.

v2.15.1

Compare Source

Patch Changes

v2.15.0

Compare Source

Minor Changes
  • #​2769 0a779904 Thanks @​penalosa! - feature: Support modules with --no-bundle

    When the --no-bundle flag is set, Wrangler now has support for uploading additional modules alongside the entrypoint. This will allow modules to be imported at runtime on Cloudflare's Edge. This respects Wrangler's module rules configuration, which means that only imports of non-JS modules will trigger an upload by default. For instance, the following code will now work with --no-bundle (assuming the example.wasm file exists at the correct path):

    // index.js
    import wasm from './example.wasm'
    
    export default {
      async fetch() {
        await WebAssembly.instantiate(wasm, ...)
        ...
      }
    }

    For JS modules, it's necessary to specify an additional module rule (or rules) in your wrangler.toml to configure your modules as ES modules or Common JS modules. For instance, to upload additional JavaScript files as ES modules, add the following module rule to your wrangler.toml, which tells Wrangler that all **/*.js files are ES modules.

    rules = [
      { type = "ESModule", globs = ["**/*.js"]},
    ]

    If you have Common JS modules, you'd configure Wrangler with a CommonJS rule (the following rule tells Wrangler that all .cjs files are Common JS modules):

    rules = [
      { type = "CommonJS", globs = ["**/*.cjs"]},
    ]

    In most projects, adding a single rule will be sufficient. However, for advanced usecases where you're mixing ES modules and Common JS modules, you'll need to use multiple rule definitions. For instance, the following set of rules will match all .mjs files as ES modules, all .cjs files as Common JS modules, and the nested/say-hello.js file as Common JS.

    rules = [
      { type = "CommonJS", globs = ["nested/say-hello.js", "**/*.cjs"]},
      { type = "ESModule", globs = ["**/*.mjs"]}
    ]

    If multiple rules overlap, Wrangler will log a warning about the duplicate rules, and will discard additional rules that matches a module. For example, the following rule configuration classifies dep.js as both a Common JS module and an ES module:

    rules = [
      { type = "CommonJS", globs = ["dep.js"]},
      { type = "ESModule", globs = ["dep.js"]}
    ]

    Wrangler will treat dep.js as a Common JS module, since that was the first rule that matched, and will log the following warning:

    ▲ [WARNING] Ignoring duplicate module: dep.js (esm)
    

    This also adds a new configuration option to wrangler.toml: base_dir. Defaulting to the directory of your Worker's main entrypoint, this tells Wrangler where your additional modules are located, and determines the module paths against which your module rule globs are matched.

    For instance, given the following directory structure:

    - wrangler.toml
    - src/
      - index.html
      - vendor/
        - dependency.js
      - js/
        - index.js
    

    If your wrangler.toml had main = "src/js/index.js", you would need to set base_dir = "src" in order to be able to import src/vendor/dependency.js and src/index.html from src/js/index.js.

Patch Changes
  • #​2957 084b2c58 Thanks @​esimons! - fix: Respect querystring params when calling .fetch on a worker instantiated with unstable_dev

    Previously, querystring params would be stripped, causing issues for test cases that depended on them. For example, given the following worker script:

    export default {
    	fetch(req) {
    		const url = new URL(req.url);
    		const name = url.searchParams.get("name");
    		return new Response("Hello, " + name);
    	}
    };

    would fail the following test case:

    const worker = await unstable_dev("script.js");
    const res = await worker.fetch("http://worker?name=Walshy");
    const text = await res.text();
    // Following fails, as returned text is 'Hello, null'
    expect(text).toBe("Hello, Walshy");
  • #​2840 e311bbbf Thanks @​mrbbot! - fix: make WRANGLER_LOG case-insensitive, warn on unexpected values, and fallback to log if invalid

    Previously, levels set via the WRANGLER_LOG environment-variable were case-sensitive.
    If an unexpected level was set, Wrangler would fallback to none, hiding all logs.
    The fallback has now been switched to log, and lenient case-insensitive matching is used when setting the level.

  • #​2735 3f7a75cc Thanks @​JacobMGEvans! - Fix: Generate Remote URL
    Previous URL was pointing to the old cloudflare/templates repo,
    updated the URL to point to templates in the workers-sdk monorepo.

v2.14.0

Compare Source

Minor Changes
  • #​2914 9af1a640 Thanks @​edevil! - feat: add support for send email bindings

    Support send email bindings in order to send emails from a worker. There
    are three types of bindings:

    • Unrestricted: can send email to any verified destination address.
    • Restricted: can only send email to the supplied destination address (which
      does not need to be specified when sending the email but also needs to be a
      verified destination address).
    • Allowlist: can only send email to the supplied list of verified destination
      addresses.
Patch Changes
  • #​2931 5f6c4c0c Thanks @​Skye-31! - Fix: Pages Dev incorrectly allowing people to turn off local mode

    Local mode is not currently supported in Pages Dev, and errors when people attempt to use it. Previously, wrangler hid the "toggle local mode" button when using Pages dev, but this got broken somewhere along the line.

v2.13.0

Compare Source

Minor Changes
  • #​2905 6fd06241 Thanks @​edevil! - feat: support external imports from cloudflare:... prefixed modules

    Going forward Workers will be providing built-in modules (similar to node:...) that can be imported using the cloudflare:... prefix. This change adds support to the Wrangler bundler to mark these imports as external.

wrangler deployments view [deployment-id] will get the details of a deployment, including bindings and usage model information.
This information can be used to help debug bad deployments.

wrangler rollback [deployment-id] will rollback to a specific deployment in the runtime. This will be useful in situations like recovering from a bad
deployment quickly while resolving issues. If a deployment id is not specified wrangler will rollback to the previous deployment. This rollback only changes the code in the runtime and doesn't affect any code or configurations
in a developer's local setup.

wrangler deployments list will list the 10 most recent deployments. This command originally existed as wrangler deployments

example of view <deployment-id> output:

v2.12.3

Compare Source

Patch Changes
  • #​2884 e33bea9b Thanks @​WalshyDev! - Changed console.debug for logger.debug in Pages uploading. This will ensure the debug logs are only sent when debug logging is enabled with WRANGLER_LOG=debug.
  • #​2878 6ebb23d5 Thanks @​rozenmd! - feat: Add D1 binding support to Email Workers

    This PR makes it possible to query D1 from an Email Worker, assuming a binding has been setup.

    As D1 is in alpha and not considered "production-ready", this changeset is a patch, rather than a minor bump to wrangler.

v2.12.2

Compare Source

Patch Changes

v2.12.1

Compare Source

Patch Changes
  • #​2839 ad4b123b Thanks @​mrbbot! - fix: remove vitest from wrangler init's generated tsconfig.json types array

    Previously, wrangler init generated a tsconfig.json with "types": ["@&#8203;cloudflare/workers-types", "vitest"], even if Vitest tests weren't generated.
    Unlike Jest, Vitest doesn't provide global APIs by default, so there's no need for ambient types.

  • #​2806 8d462c0c Thanks @​GregBrimble! - feat: Add --outdir as an option when running wrangler pages functions build.

    This deprecates --outfile when building a Pages Plugin with --plugin.

    When building functions normally, --outdir may be used to produce a human-inspectable format of the _worker.bundle that is produced.

  • #​2806 8d462c0c Thanks @​GregBrimble! - Enable bundling in Pages Functions by default.

    We now enable bundling by default for a functions/ folder and for an _worker.js in Pages Functions. This allows you to use external modules such as Wasm. You can disable this behavior in Direct Upload projects by using the --no-bundle argument in wrangler pages publish and wrangler pages dev.

  • #​2836 42fb97e5 Thanks @​GregBrimble! - fix: preserve the entrypoint filename when running wrangler publish --outdir <dir>.

    Previously, this entrypoint filename would sometimes be overwritten with some internal filenames. It should now be based off of the entrypoint you provide for your Worker.

  • #​2828 891ddf19 Thanks @​GregBrimble! - fix: Bring pages dev logging in line with dev proper's

    wrangler pages dev now defaults to logging at the log level (rather than the previous warn level), and the pages prefix is removed.

  • #​2855 226e63fa Thanks @​GregBrimble! - fix: --experimental-local with wrangler pages dev

    We previously had a bug which logged an error (local worker: TypeError: generateASSETSBinding2 is not a function). This has now been fixed.

v2.12.0

Compare Source

Minor Changes
  • #​2810 62784131 Thanks @​mrbbot! - chore: upgrade @miniflare/tre to 3.0.0-next.12, incorporating changes from 3.0.0-next.11

    Notably, this brings the following improvements to wrangler dev --experimental-local:

    • Adds support for Durable Objects and D1
    • Fixes an issue blocking clean exits and script reloads
    • Bumps to better-sqlite3@&#8203;8, allowing installation on Node 19
  • #​2665 4756d6a1 Thanks @​alankemp! - Add new [unsafe.metadata] section to wrangler.toml allowing arbitary data to be added to the metadata section of the upload
Patch Changes
  • #​2539 3725086c Thanks @​GregBrimble! - feat: Add support for the nodejs_compat Compatibility Flag when bundling a Worker with Wrangler

    This new Compatibility Flag is incompatible with the legacy --node-compat CLI argument and node_compat configuration option. If you want to use the new runtime Node.js compatibility features, please remove the --node-compat argument from your CLI command or your config file.

v2.11.1

Compare Source

Patch Changes
  • #​2795 ec3e181e Thanks @​penalosa! - fix: Adds a duplex: "half" property to R2 fetch requests with stream bodies in order to be compatible with undici v5.20
  • #​2789 4ca8c0b0 Thanks @​GregBrimble! - fix: Support overriding the next URL in subsequent executions with next("/new-path") from within a Pages Plugin

v2.11.0

Compare Source

Minor Changes
  • #​2651 a9adfbe7 Thanks @​penalosa! - Previously, wrangler dev would not work if the root of your zone wasn't behind Cloudflare. This behaviour has changed so that now only the route which your Worker is exposed on has to be behind Cloudflare.
  • #​2708 b3346cfb Thanks @​Skye-31! - Feat: Pages now supports Proxying (200 status) redirects in it's _redirects file

    This will look something like the following, where a request to /users/123 will appear as that in the browser, but will internally go to /users/[id].html.

    /users/:id /users/[id] 200
    
Patch Changes
  • #​2766 7912e63a Thanks @​mrbbot! - fix: correctly detect service-worker format when using typeof module

    Wrangler automatically detects whether your code is a modules or service-worker format Worker based on the presence of a default export. This check currently works by building your entrypoint with esbuild and looking at the output metafile.

    Previously, we were passing format: "esm" to esbuild when performing this check, which enables format conversion. This may introduce export default into the built code, even if it wasn't there to start with, resulting in incorrect format detections.

    This change removes format: "esm" which disables format conversion when bundling is disabled. See https://esbuild.github.io/api/#format for more details.

  • #​2780 80f1187a Thanks @​GregBrimble! - fix: Ensure we don't mangle internal constructor names in the wrangler bundle when building with esbuild

    Undici changed how they referenced FormData, which meant that when used in our bundle process, we were failing to upload multipart/form-data bodies. This affected wrangler pages publish and wrangler publish.

  • #​2720 de0cb57a Thanks @​JacobMGEvans! - Fix: Upgraded to ES2022 for improved compatibility
    Upgraded worker code target version from ES2020 to ES2022 for better compatibility and unblocking of a workaround related to issue #​2029. The worker runtime now uses the same V8 version as recent Chrome and is 99% ES2016+ compliant. The only thing we don't support on the Workers runtime, the remaining 1%, is the ES2022 RegEx feature as seen in the compat table for the latest Chrome version.

    Compatibility table: https://kangax.github.io/compat-table/es2016plus/

    resolves #​2716

v2.10.0

Compare Source

Minor Changes

Configuration

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

🚦 Automerge: Enabled.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jun 2, 2023
@changeset-bot
Copy link

changeset-bot bot commented Jun 2, 2023

🦋 Changeset detected

Latest commit: 45e08fe

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
graphql-modules Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions
Copy link
Contributor

github-actions bot commented Jun 2, 2023

💻 Website Preview

The latest changes are available as preview in: https://868bc569.graphql-modules.pages.dev

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 547b8ad to 512477d Compare June 2, 2023 14:31
@ardatan ardatan merged commit d49191d into master Jun 2, 2023
@ardatan ardatan deleted the renovate/all-minor-patch branch June 2, 2023 14:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant