-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
"yarn add newrelic" fails with "Couldn't find a package.json" error #1215
Comments
Confirmed that this still fails with yarn 0.16.0 |
Just tried to reproduce myself, but couldn't: $ mkdir foo
$ cd foo
$ yarn init
blah blah blah
$ yarn add newrelic
yarn add v0.16.0
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching packages...
[3/4] Linking dependencies...
[4/4] Building fresh packages...
success Saved lockfile.
success Saved 20 new dependencies.
├─ agent-base@1.0.2
├─ concat-stream@1.5.2
│ ├─ isarray@1.0.0
│ └─ readable-stream@2.0.6
├─ core-util-is@1.0.2
├─ debug@2.2.0
├─ extend@3.0.0
├─ https-proxy-agent@0.3.6
├─ inherits@2.0.3
├─ isarray@0.0.1
├─ json-stringify-safe@5.0.1
├─ ms@0.7.1
├─ newrelic@1.31.0
├─ process-nextick-args@1.0.7
├─ readable-stream@1.1.14
├─ semver@4.3.6
├─ string_decoder@0.10.31
├─ typedarray@0.0.6
├─ util-deprecate@1.0.2
└─ yakaa@1.0.1
Done in 5.89s. Node version |
I'm on Node 6.2.0, maybe that's the issue? On Oct 18, 2016 9:30 PM, "Alex LaFroscia" notifications@github.com wrote:
|
This is no longer reproducible on master. Closing, let me know if this is still an issue for you. |
I just ran into this problem, but with The error I’m getting is:
This is on |
still happening with yarn 0.18.1, node 6.10.0 |
Have this with yarn 0.27.5 node 7.2.0, happens with |
Fixed on master via #4046, please try the nightlies. |
Do you want to request a feature or report a bug?
bug
What is the current behavior?
yarn add newrelic
fails withI suspect it's a problem with
bundledDependencies
in thenewrelic
package.If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
Please mention your node.js, yarn and operating system version.
The text was updated successfully, but these errors were encountered: