question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Problem with 2.2.23 npm release?

See original GitHub issue

Hi,

This morning I detected an issue in our deployment pipeline that seems to be related to the 2.2.23/2.2.24 releases that occured a few hours ago.

Here is the error:

Error: Cannot find module 'bodybuilder'
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
    at Function.Module._load (internal/modules/cjs/loader.js:562:25)
    at Module.require (internal/modules/cjs/loader.js:692:17)
    at require (internal/modules/cjs/helpers.js:25:18)
    at Object.<anonymous> (/app/build/server/core/graphql/webpack:/external "bodybuilder":1:1)
    at __webpack_require__ (/app/build/server/core/graphql/webpack:/webpack/bootstrap:19:1)
    at Module.<anonymous> (/app/build/server/core/graphql/writeIntrospectionFiles.js:9009:29)
    at __webpack_require__ (/app/build/server/core/graphql/webpack:/webpack/bootstrap:19:1)
    at /app/build/server/core/graphql/webpack:/webpack/bootstrap:83:1
    at Object.<anonymous> (/app/build/server/core/graphql/writeIntrospectionFiles.js:88:10)

The app depends on 2.2.* and got the 2.2.23 version from npm.

Extract of the package-lock.json:

    "bodybuilder": {
      "version": "2.2.23",
      "resolved": "https://registry.npmjs.org/bodybuilder/-/bodybuilder-2.2.23.tgz",
      "integrity": "sha512-sQUrEPFMY0/8rpIFq8U0QL0tlRX9lGZfuXmte9yo/9mH1LpD3U5Um4s5V6q0ARkuCf82070RHTuACQq1X+n2sQ==",

Here is a diff of a tree of node_modules/bodybuilder of an application already installed before yesterday and the new one I get today: the lib directory is gone.

https://www.diffchecker.com/etAJCbe6

Is this an issue with the release on npm?

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:5
  • Comments:14 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
danpazcommented, Nov 20, 2020

@uyu423 I’m thinking I’ll actually unpublish those two versions since they’re completely broken.

1reaction
danpazcommented, Nov 20, 2020

I’ve published 2.2.25 which includes the lib files and should fix the issue. Could someone confirm please?

Read more comments on GitHub >

github_iconTop Results From Across the Web

"npm install" removes nearly all other dependencies #17929
When running "npm install" nearly all dependencies got removed. This happens on npm 5.3.0. There was formerly an issue opened and already ...
Read more >
npm WARN deprecated tar@2.2.2: This version of tar is no ...
This is not an error. Your tar is outdated. To fix this issue run this command :- npm i tar and enter ok....
Read more >
Tip: Click on a version number to view a previous ... - npm
Tip: Click on a version number to view a previous version's package page ...
Read more >
npm warn deprecated tar@2.2.2: this version of tar ... - You.com
The warning npm WARN deprecated tar@2.2.2: This version of tar is no longer supported occurs when installing `create-react-app` or some other package that...
Read more >
Yarn: A package manager for Node.js - Pluralsight
To solve this issue, Yarn uses a lockfile ( yarn.lock ) to ensure that everyone has the same version of every single file,...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found