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

fix(deps): update dependency synckit to ^0.10.0 #299

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
synckit ^0.6.0 -> ^0.10.0 age adoption passing confidence

Release Notes

un-ts/synckit (synckit)

v0.10.0

Compare Source

Minor Changes
  • #​199 7a5f1bd Thanks @​nwidynski! - feat: add support for --experimental-strip-types

    Introducing the node runner, which will replace ts-node as the new default:

    • when running on Node 22 with the --experimental-strip-types
      flag enabled via NODE_OPTIONS env or cli args
    • or when running on Node 23+ without --no-experimental-strip-types
      flag enabled via NODE_OPTIONS env or cli args

    An error will be thrown when attempting to run with node on unsupported versions (<22).
    On these versions, the default runner remains ts-node when available.

v0.9.2

Compare Source

Patch Changes

v0.9.1

Compare Source

Patch Changes

v0.9.0

Compare Source

Minor Changes
Patch Changes

v0.8.8

Compare Source

Patch Changes
  • #​148 7b6a0eb Thanks @​JounQin! - feat: migrate @pkgr/utils to lite @pkgr/core - This will make the whole package much more smaller

v0.8.7

Compare Source

Patch Changes
  • #​145 b2affa0 Thanks @​JounQin! - feat: add new globalShims option, what means you can env SYNCKIT_GLOBAL_SHIMS=1 to enable auto polyfilling for some modules, for example: fetch from node-fetch, performance from node:perf_hooks.

    You can also pass a custom globalShims option as GlobalShim Array to custom your own shims:

    export interface GlobalShim {
      moduleName: string
      /**
       * `undefined` means side effect only
       */
      globalName?: string
      /**
       * 1. `undefined` or empty string means `default`, for example:
       * ```js
       * import globalName from 'module-name'
       * ```
       *
       * 2. `null` means namespaced, for example:
       * ```js
       * import * as globalName from 'module-name'
       * ```
       *
       */
      named?: string | null
      /**
       * If not `false`, the shim will only be applied when the original `globalName` unavailable,
       * for example you may only want polyfill `globalThis.fetch` when it's unavailable natively:
       * ```js
       * import fetch from 'node-fetch'
       *
       * if (!globalThis.fetch) {
       *   globalThis.fetch = fetch
       * }
       * ```
       */
      conditional?: boolean
    }

    You can aslo reuse the exported DEFAULT_GLOBAL_SHIMS_PRESET for extanding:

    import { DEFAULT_GLOBAL_SHIMS_PRESET, createSyncFn } from 'synckit'
    
    const syncFn = createSyncFn(require.resolve('./worker'), {
      globalShims: [
        ...DEFAULT_GLOBAL_SHIMS_PRESET,
        // your own shim here
      ],
    })

v0.8.6

Compare Source

Patch Changes

v0.8.5

Compare Source

Patch Changes

v0.8.4

Compare Source

Patch Changes

v0.8.3

Compare Source

Patch Changes

v0.8.2

Compare Source

Patch Changes

v0.8.1

Compare Source

Patch Changes

v0.8.0

Compare Source

Minor Changes

v0.7.3

Compare Source

Patch Changes

v0.7.2

Compare Source

Patch Changes
  • 1101ede Thanks @​JounQin! - chore: add donate and funding fields, update node engine field

v0.7.1

Compare Source

Patch Changes

v0.7.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 is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

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

Copy link

changeset-bot bot commented Jan 23, 2024

⚠️ No Changeset found

Latest commit: 422ef13

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

@renovate renovate bot force-pushed the renovate/synckit-0.x branch 2 times, most recently from 48ee292 to 2be3ec8 Compare January 27, 2024 20:46
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 7 times, most recently from 4c1c6c7 to 192194a Compare March 23, 2024 12:32
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 3 times, most recently from 8a8719d to e14c49d Compare April 1, 2024 10:06
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 7 times, most recently from 5705446 to 5ce6091 Compare April 13, 2024 13:13
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from 5ce6091 to 49a0b22 Compare April 19, 2024 06:14
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 3 times, most recently from 31a2a5a to ee15af3 Compare May 8, 2024 18:50
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 2 times, most recently from fc1234c to 6588f79 Compare May 25, 2024 00:23
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from 6588f79 to 1b9f41d Compare June 10, 2024 03:11
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 2 times, most recently from 5c2f240 to 421ce89 Compare June 23, 2024 09:52
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from 421ce89 to 868f328 Compare July 1, 2024 01:37
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from 0b3be2d to 78c1da3 Compare November 11, 2024 00:30
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 6 times, most recently from 0613aa2 to b1a1182 Compare November 19, 2024 00:40
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from b1a1182 to 566995a Compare November 25, 2024 20:35
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from 566995a to 8b0d3b7 Compare December 2, 2024 22:24
@renovate renovate bot changed the title fix(deps): update dependency synckit to ^0.9.0 fix(deps): update dependency synckit to ^0.9.0 - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/synckit-0.x branch December 8, 2024 18:37
@renovate renovate bot changed the title fix(deps): update dependency synckit to ^0.9.0 - autoclosed fix(deps): update dependency synckit to ^0.9.0 Dec 8, 2024
@renovate renovate bot reopened this Dec 8, 2024
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 2 times, most recently from 8b0d3b7 to 07c7fc1 Compare December 13, 2024 18:06
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 2 times, most recently from 54cbb95 to cdff103 Compare January 13, 2025 19:11
@renovate renovate bot force-pushed the renovate/synckit-0.x branch 9 times, most recently from cd4c39d to b6d60ca Compare January 25, 2025 05:01
@renovate renovate bot force-pushed the renovate/synckit-0.x branch from b6d60ca to 422ef13 Compare March 20, 2025 12:58
@renovate renovate bot changed the title fix(deps): update dependency synckit to ^0.9.0 fix(deps): update dependency synckit to ^0.10.0 Mar 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants