Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 8141419
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: June 6, 20262026-06-06T12:30:06+00:00 2026-06-06T12:30:06+00:00

I have a deployed version 0.6 of Node.js with a considerable number of packages

  • 0

I have a deployed version 0.6 of Node.js with a considerable number of packages installed for various projects.

Is there a straight-forward way to check all of the packages that were installed using NPM to see if they support Node.js v 0.8.x?

I can see that the package.json files should say what version of Node they are for though I’m guessing that many will not include this – so I’m really only interested in packages that say they are definately not compatible with Node v 0.8.x

e.g. They have something like this in package.json:

"engines": {
  "node": "<0.8.0"
},

or

"engines": {
  "node": "=0.6.*"
},

I just want a simple list of packages that are incompatible.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-06-06T12:30:09+00:00Added an answer on June 6, 2026 at 12:30 pm

    Try this in the base directory of your application:

    find . -name package.json -exec node -e 'var e = JSON.parse(require("fs").readFileSync(process.argv[1]))["engines"]; if (e && e.node) { var bad = false; if (e.node.match(/<\s*0\.[0-8]([^.]|\.0)/)) bad = true; if (e.node.match(/(^|[^>])=\s*0\.[^8]/)) bad = true; if (bad) console.log(process.argv[1], "appears no good (", e.node, ")") }' '{}' \;
    

    Translation into normal style:

    var fs = require("fs");
    
    var contents = fs.readFileSync(process.argv[1]);
    var package = JSON.parse(contents);
    var engines = package.engines;
    
    if (engines && engines.node) {
        var node = engines.node,
            bad = false;
    
        if (node.match(/<\s*0\.[0-8]([^.]|\.0)/)) {
            // Looks like "< 0.8.0" or "< 0.8" (but not "< 0.8.1").
            bad = true;
        }
    
        if (node.match(/(^|[^>])=\s*0\.[^8]/)) {
            // Looks like "= 0.7" or "= 0.9" (but not ">= 0.6").
            bad = true;
        }
    
        if (bad) {
            console.log(process.argv[1], "appears no good (", node, ")");
        }
    }
    

    We then use find to run this on every package.json we can find.

    Here’s what I get when I run it over my express-template.coffee package:

    ./node_modules/jade/node_modules/commander/package.json appears no good ( >= 0.4.x < 0.8.0 )
    ./node_modules/mocha/node_modules/commander/package.json appears no good ( >= 0.4.x < 0.8.0 )
    ./node_modules/mocha/package.json appears no good ( >= 0.4.x < 0.8.0 )
    

    It seems TJ has a thing against 0.8 😉

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I have a strange problem with lxml when using the deployed version of my
I have deployed a new version of an ASP.NET webservice. The IIS logfile reports
I have deployed to version 1.0 to Apple store. And i'm getting ready for
I have a project (a version of which has already been deployed) in the
Have deployed numerous report parts which reference the same view however one of them
I have deployed an application on the IIS server, as per my requirement i
I have deployed a PHP application on my tomcat server(Tomcat 6.0).Previously I was using
We have deployed a java webapplication in Elastic Beanstalk with the minimum instance count
i have deployed my wcf service on IIS.. Its giving me this error when
I have deployed my website to an .net 2.0.50727 hosting, and the page with

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.