Skip to content

update dependencies, fix test case #204

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

Merged
merged 2 commits into from
Feb 24, 2022

Conversation

bobfang
Copy link
Contributor

@bobfang bobfang commented Feb 17, 2022

Updating package dependencies to remediate whitesource scan findings

  • Using watchify to invoke browserify on the example app instead of using express-browserify (removed)
  • Added npm-run-all to run watchify and server.js for example app in local development mode (old dev script didn't exist anyway)
  • Updated mocha to latest version
  • Updated nodeify-fetch to v2.2.2
    • This broke the recognize-file should transcribe files via URL test
    • Fixed test case in recognize-file.js related to nodeify-fetch API changes between v1.0.1 to v.2.2.2
  • Removed npm from dependencies
  • Updated main package.json version to 0.39.1
  • Updated example package.json to require watson-speech ^0.39.0 so it pulls the latest available release (currently v0.39.0) and will receive update via v0.39.1 (this PR)
Checklist
  • npm test passes
  • changelog updated
Tests

Firefox 97.0 (Mac OS 10.15): Executed 42 of 42 SUCCESS (10.202 secs / 10.163 secs)
TOTAL: 42 SUCCESS

@CLAassistant
Copy link

CLAassistant commented Feb 17, 2022

CLA assistant check
All committers have signed the CLA.

// new behavior https://github.com/bergos/nodeify-fetch/blob/v2.2.2/lib/patchResponse.js
// seems like we just have to check if the body is readable
if (response.body.readable) {
return response.body
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should use semicolons here. we'll need to check and make sure we are linting on pre-commit

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

did a npm run lint and it didn't find anything. proceeded to add semicolons in the next commit manually.

@bobfang bobfang requested a review from jeff-arn February 18, 2022 03:31
Copy link
Contributor

@apaparazzi0329 apaparazzi0329 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mediumTaj mediumTaj merged commit da51815 into watson-developer-cloud:master Feb 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants