Skip to content
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

NPM test unknown error #4961

Closed
DaAwesomeP opened this issue Jul 13, 2015 · 12 comments
Closed

NPM test unknown error #4961

DaAwesomeP opened this issue Jul 13, 2015 · 12 comments

Comments

@DaAwesomeP
Copy link
Contributor

DaAwesomeP commented Jul 13, 2015

I can't figure out what the problem is with my package.json. I get the following error when running npm test:

$ npm test

> cdnjs@1.0.0 test c:\GitHub\cdnjs
> vows

to start, pass the "run" arg
··✗·✗···· ···········


    npmFileMap validation - simple
      ✗ This is a valid npm file map
        » expected true,
        got      false (==) // auto-update-test.js:36

    npmFileMap validation - arrays
      ✗ valid array of file maps
        » expected true,
        got      false (==) // auto-update-test.js:72
  ✗ Broken » 18 honored ∙ 2 broken (0.018s)
  npm ERR! Test failed.  See above for more details.

Here is my package.json:

{
  "name": "upb",
  "description": "A NodeJS, Bower, browser, AMD, and CommonJS library that generates and decodes UPB (Universal Powerline Bus) commands.",
  "keywords": [
    "upb",
    "library",
    "universal",
    "powerline",
    "bus",
    "command",
    "lib",
    "lighting",
    "switches",
    "control"
  ],
  "homepage": "https://github.com/DaAwesomeP/node-upb/",
  "bugs": "https://github.com/DaAwesomeP/node-upb/issues",
  "license": "Apache-2.0",
  "maintainers": [
    {
      "name": "DaAwesomeP",
      "web": "https://daawesomep.guthub.io/"
    }
  ],
  "repositories": [
    {
      "type": "git",
      "url": "https://github.com/DaAwesomeP/node-upb.git"
    }
  ],
  "version": "1.2.3",
  "npmName": "upb",
  "npmFileMap": [
    {
      "basePath": "/",
      "files": [
        "upb.js"
      ]
    },
    {
      "basePath": "/dist/",
      "files": [
        ".js",
        ".map"
      ]
    }
  ],
  "filename": "upb.min.js",
  "namespace": "upb"
}

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@PeterDaveHello
Copy link
Contributor

Thanks for your report @DaAwesomeP, will take a look at it.

@DaAwesomeP
Copy link
Contributor Author

@PeterDaveHello is this package.json technically correct (the test simply made an error)? I'd like to submit it now if I can.

@PeterDaveHello
Copy link
Contributor

@DaAwesomeP yep!

@DaAwesomeP
Copy link
Contributor Author

The CI test passed in #4967. I see that that was using NodeJS. I was using io.js v2.3.3 and NPM v2.11.3. There must be an incompatible dependency (that needs to be updated) or some other change in io.js from NodeJS.

@PeterDaveHello
Copy link
Contributor

Oh okay, we don't support iojs yet.

@PeterDaveHello PeterDaveHello changed the title NPM test unknown error [iojs support]NPM test unknown error Jul 14, 2015
@PeterDaveHello PeterDaveHello changed the title [iojs support]NPM test unknown error NPM test unknown error Jul 14, 2015
@PeterDaveHello
Copy link
Contributor

I have no problem on Ubuntu 14.04.2 LTS 64bit with io.js v2.3.2/2.3.3/2.3.4 and npm v2.11.3/2.11.3/2.12.1
Would you please provide info in more detail? Like operating system or something else?

@DaAwesomeP
Copy link
Contributor Author

I have Windows 8.1 Pro x64 and I'm pretty sure Visual Studio Express 2013. What dependencies have native modules or haven't been updated fully in package.json? They're probably the problem.

On Jul 14, 2015, at 2:00 AM, "Peter Dave Hello" notifications@github.com wrote:

I have no problem on Ubuntu 14.04.2 LTS 64bit with io.js v2.3.2/2.3.3/2.3.4 and npm v2.11.3/2.11.3/2.12.1
Would you please provide info in more detail? Like operating system or something else?


Reply to this email directly or view it on GitHub.

@PeterDaveHello
Copy link
Contributor

@cdnjs/intern : @Amomo, @Piicksarn please test if you'll get the same problem in Windows, thanks.

@DaAwesomeP
Copy link
Contributor Author

I haven't done much with CDNjs since I posted this issue a while ago, but I think that I still have a local copy of my fork in the same state if that's any use.

@Mottie
Copy link
Contributor

Mottie commented Jan 20, 2016

I'm seeing this same issue on my computer using Windows 10 x64 v1511 OS Build 10586.63

When I add a console.log to the isValidPath function in the auto-update.js file so the function looks like this:

    var isValidPath = function(p) {
        if (p !== null) { //don't allow parent dir access, or tricky paths
            p = p.replace(/\/+/g, '/'); //dont penalize for consequtive path seperators
            console.log( p, path.normalize(p) );
            return p === path.normalize(p);
        }
        return false
    };

I see this output:

$ npm test

> cdnjs@1.0.0 test D:\Repos\cdnjs
> vows

to start, pass the "run" arg
··/dist/ \dist\
✗·/dist/ \dist\
✗··/dist/ \dist\
·· ····························


    npmFileMap validation - simple
      ✗ This is a valid npm file map
        » expected true,
        got      false (==) // auto-update-test.js:36

    npmFileMap validation - arrays
      ✗ valid array of file maps
        » expected true,
        got      false (==) // auto-update-test.js:72
  ✗ Broken » 35 honored ∙ 2 broken (0.025s)
  npm ERR! Test failed.  See above for more details.

@PeterDaveHello PeterDaveHello assigned Amomo and unassigned Piicksarn Jan 20, 2016
@PeterDaveHello
Copy link
Contributor

@Amomo please take a look.

@xtuc
Copy link
Member

xtuc commented Feb 20, 2020

Closing for lack of activity. Feel free to open a new issue if needed

@xtuc xtuc closed this as completed Feb 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants