-
Notifications
You must be signed in to change notification settings - Fork 390
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
NewRelic crashes app with symlinked node modules #153
Comments
Whoah, that's no good. Can you describe how you symlinked the module into your project? I often use Thanks! |
This has occured using both The project is: DavidSouther/flipflops@8c86efc The library is: You will need to Note also, as I think more about this, I only tested this in passenger mode. BRB more testing. |
Interesting... this looks like it might be a passenger issue. |
Definitely a passenger issue; New Relic just happened to be the first thing loading! |
|
@DavidSouther thanks for investigating! |
Update s3-client semver range to skip 3.192.0
Update s3-client semver range to skip 3.192.0
While developing a library, NewRelic fails at startup when the library is symlinked for development.
It seems to be recursing infinitely in shimmer.
I narrowed it down to the symlink issue by isolating changing the dependency as a symlink vs cp -r into node modules. Can provide more details to isolate a minimal test case as needed.
The text was updated successfully, but these errors were encountered: