Skip to content

fix(deps): update dependency inversify to v6.2.2 #328

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 15, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
inversify (source) 6.0.2 -> 6.2.2 age adoption passing confidence

Release Notes

inversify/InversifyJS (inversify)

v6.2.2

Compare Source

  • Solved issue with npm registry.

v6.2.1

Compare Source

Fixed
  • Added missing LazyServiceIdentifer.

v6.2.0

Compare Source

Added
  • Added interfaces.GetAllOptions.
Changed
  • Updated container.getAll with options optional param.
  • Updated container.getAllAsync with options optional param.
  • Updated interfaces.NextArgs with optional isOptional param.
  • Updated container with tryGet.
  • Updated container with tryGetAsync.
  • Updated container with tryGetTagged.
  • Updated container with tryGetTaggedAsync.
  • Updated container with tryGetNamed.
  • Updated container with tryGetNamedAsync.
  • Updated container with tryGetAll.
  • Updated container with tryGetAllAsync.
  • Updated container with tryGetAllTagged.
  • Updated container with tryGetAllTaggedAsync.
  • Updated container with tryGetAllNamed.
  • Updated container with tryGetAllNamedAsync.

v6.1.6

Compare Source

Fixed
  • Fixed unexpected property access while running planning checks on injected base types.
  • Updated ESM sourcemaps to refelct the right source code files.

v6.1.5

Compare Source

Changed
  • Updated library to import reflect-metadata. Importing reflect-metadata before bootstraping a module in the userland is no longer required.
Fixed
  • Updated ESM build to provide proper types regardless of the ts resolution module strategy in the userland.
  • Fixed container to properly resolve async .toService bindings.
  • Fixed .toService binding to properly disable caching any values.

v6.1.4

Compare Source

Changed
  • Updated planner with better error description when a binding can not be properly resolved.
Fixed
  • Updated container to allow deactivating singleton undefined values.
  • Updated ESM build to be compatible with both bundler and NodeJS module resolution algorithms.

v6.1.3

Compare Source

Fixed
  • Updated ESM build with missing types.

v6.1.2

Compare Source

Changed
  • Updated package.json to include the exports field for better bundler support.
Fixed
  • Updated fetch metadata flows with better error descriptions.

v6.1.1

Compare Source

Fixed
  • Bumped @inversifyjs/common and @inversifyjs/core fixing wrong dev engines constraints.

v6.1.0

Compare Source

Changed
  • Updated ServiceIdentifier to rely on Function instead of Abstract<T>.
  • injectable decorator is no longer required.
Fixed
  • Fixed Target.getNameTag with the right type: number | string | symbol.

v6.0.3

Compare Source

Fixed

property injection tagged as @​optional no longer overrides default values with undefined.
Updated targetName to be a valid typescript@5 decorator.


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
Contributor Author

renovate bot commented Jan 15, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.1.13" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"~0.2.2" from [email protected]
npm ERR! node_modules/inversify
npm ERR!   inversify@"6.2.2" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2025-02-02T13_18_00_324Z-debug-0.log

@renovate renovate bot force-pushed the renovate/inversify-6.x branch from 3a8eee6 to c586380 Compare February 2, 2025 13:18
@renovate renovate bot changed the title fix(deps): update dependency inversify to v6.2.1 fix(deps): update dependency inversify to v6.2.2 Feb 2, 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