-
Notifications
You must be signed in to change notification settings - Fork 13
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
Noctua library chain needs to be fixed / brought up to date #577
Labels
Milestone
Comments
kltm
changed the title
Noctua library chaing needs to be fixed / brought up to date
Noctua library chain needs to be fixed / brought up to date
Aug 31, 2018
kltm
added a commit
to berkeleybop/minerva-requests
that referenced
this issue
Aug 31, 2018
kltm
added a commit
to berkeleybop/minerva-requests
that referenced
this issue
Aug 31, 2018
kltm
added a commit
to berkeleybop/minerva-requests
that referenced
this issue
Aug 31, 2018
Done so far:
|
kltm
added a commit
to berkeleybop/bbop-response-barista
that referenced
this issue
Aug 31, 2018
kltm
added a commit
to geneontology/noctua-repl
that referenced
this issue
Aug 31, 2018
kltm
added a commit
that referenced
this issue
Aug 31, 2018
Probably others, but this is the main stuff we want working right now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, some libraries seem to have not been properly transitioned between node 6 and 8, giving errors like:
Some explanation here:
https://stackoverflow.com/questions/44298322/node-8-0-0-and-npm-4-2-0-error-express-load-require-extensions-hasownproperty-is
Closure of this will be a pass of our noctua-oriented libraries and confirming that node 8.11 and npm 5.6 (more-or-less what we've agreed) are all working for tests.
@goodb
The text was updated successfully, but these errors were encountered: