This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.
npm 3: package not installed on the initial install #10637
Comments
|
@darrinholst I am also affected by the exact same issue. |
|
This is working correctly in |
cnishina
pushed a commit
to angular/protractor
that referenced
this issue
Apr 28, 2016
Cucumber allows line numbers to be passed in the filename in the form of `features/some.feature:42`. Glob expanding that results in an empty array and nothing being passed to the framework runner. This change checks for glob magic characters and only tries expanding it if found. Otherwise it just passes the filename verbatim. This was previously handled in [#2445] by stripping the line number first, but this is a more generic (non-cucumber) way to do it. Glob needed to be upgraded for this which resulted in a weird [npm 3 bug] (npm/npm#10637). Removing the rimraf package resolved this. It was only used to generate documentation which itself was removed a while ago.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've found a combination of dependencies where a top level package isn't installed on the first try. Subsequent installs will install it. I've narrowed it down to these dependencies. The first install to an empty
node_modulesresults inglobnot being installed. The debug output for the first install is here. The output for the second install is hereThe text was updated successfully, but these errors were encountered: