Skip to content
This repository was archived by the owner on Mar 5, 2025. It is now read-only.
This repository was archived by the owner on Mar 5, 2025. It is now read-only.

Depencency tree in 4.0.0-alpha.0 cannot be resolved #5382

Closed

Description

@mpetrunic

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

mpetrunic@mpetrunic-XPS-9320:~/Projects/ChainSafe/playground/web3.js$ yarn add [email protected]
yarn add v1.22.19
[1/4] Resolving packages...
warning web3 > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-personal > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-contract > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-ens > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-core > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth > web3-core-requestmanager > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-core > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-abi > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-iban > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-personal > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-contract > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-ens > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-eth-accounts > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-net > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-core > web3-providers-ipc > [email protected]: Intended to be released as alpha, does not work in current form
warning web3 > web3-core > web3-providers-ws > [email protected]: Intended to be released as alpha, does not work in current form
Couldn't find any versions for "web3-providers-base" that matches "^1.0.0"
? Please choose a version of "web3-providers-base" from this list: (Use arrow keys)
Couldn't find any versions for "web3-providers-base" that matches "^1.0.0"
? Please choose a version of "web3-providers-base" from this list: (Use arrow keys)
❯ 1.0.0-alpha.1 

Expected Behavior

Install without warnings or errors

Steps to Reproduce

yarn add [email protected]

Web3.js Version

4.0.0-alpha.0

Environment

  • Operating System: Ubuntu
  • Browser: -
  • Node.js Version: 16
  • NPM Version: yarn1

Anything Else?

No response

Activity

  1. mpetrunic commented on Aug 25, 2022

    @mpetrunic
    MemberAuthor

    Seems like 4.0.0 version of some packages was published a year ago and then deprecated: https://www.npmjs.com/package/web3-eth/v/4.0.0

    Short term fix:

    • remove version range to force resolution of alpha package

    Long term:
    open support ticket with npm to remove those 4.0.0 versions as they will prevent us from publishing 4.0.0 cc @GregTheGreek

  2. GregTheGreek commented on Aug 25, 2022

    @GregTheGreek
    Contributor

    I've emailed NPM to remove the following package and respective versions:

  3. jdevcs commented on Aug 25, 2022

    @jdevcs
    Contributor

    Fix for 4.0.0-alpha.0 :

    Adding following explicitly to package.json users can fix yarn to skip using old deprecated packages and use specified ones:

    "resolutions": {
        "web3-providers-http": "4.0.0-alpha.1",
        "web3-utils": "4.0.0-alpha.1",
        "web3-eth": "4.0.0-alpha.1"
      }
    

    This resolves dependency tree with: yarn add [email protected]

    We will also post alpha patch bump, so users will not need above mentioned temp fix with that.

  4. self-assigned this
    on Aug 25, 2022
  5. jdevcs commented on Aug 25, 2022

    @jdevcs
    Contributor

    4.x Alpha patch bump has been published:
    https://www.npmjs.com/package/web3/v/4.0.1-alpha.0
    https://github.com/ChainSafe/web3.js/releases/tag/v4.0.1-alpha.0
    With this yarn is not resolving to deprecated package. yarn add [email protected]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

4.x4.0 relatedBugAddressing a bug

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions