wordpress/create-block ERROR

  • Resolved Imagedavavalos

    (@davavalos)


    1 week, 1 day ago

    I keep getting the same error and the dependencies fail to install:

    npm error code E404
    npm error 404 Not Found – GET https://registry.npmjs.org/@wordpress%2fvips – Not found
    npm error 404
    npm error 404 The requested resource ‘@wordpress/vips@^1.0.0-prerelease’ could not be found or you do not have permission to access it.

    When trying to use either the 

    npx @wordpress/create-block@latest

    or

    npm install @wordpress/scripts --save-dev

    I made sure to use the latest LTS (Long Term Support) version of Node.js. This is on Mac. I’ve never had any issues with these packages before today.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Moderator Imagethreadi

    (@threadi)

    1 week, 1 day ago

    You don’t seem to be the only one: https://github.com/WordPress/gutenberg/issues/75686 – I think this should be reported as a separate issue and then investigated by the Gutenberg team.

    Imagemitchelljarboe

    (@mitchelljarboe)

    1 week ago

    You are not the only one
    Wake up WordPress, you are getting noticed

    Thread Starter Imagedavavalos

    (@davavalos)

    1 week ago

    Here’s the temporary fix I found on GitHub for now since it’s still bugged for anyone trying to use this.

    Run npx @wordpress/create-block@latest

    After setup, and once you get the error, open the files created and navigate to the package.json. Add the following above “dependencies”

    ”overrides”: {
           “@wordpress/upload-media”: “0.24.0”
    },

    then cd back to the folder that contains your custom block and run npm install @wordpress/scripts –save-dev

    You should be able to npm run start and build after.

    ImageKJ Roelke

    (@kjroelke)

    1 week ago

    Thanks @davavalos! Overrides works….but it doesn’t do anything about the new vulnerabilities.

    Issue can be followed on Github here: https://github.com/WordPress/gutenberg/issues/75718

    Imagerobert0508

    (@robert0508)

    3 days, 21 hours ago

    It’s just an npm registry/cache issue — the @wordpress/vips prerelease package isn’t available right now.

    Clear the npm cache, reset the registry, and try the install again — it usually fixes the problem.

    Thread Starter Imagedavavalos

    (@davavalos)

    3 days, 11 hours ago

    It was a bug that WordPress has now fixed. Check the linked GitHub issue above for more information. Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.