Update pdf2json: 1.1.7 → 1.3.0 (minor)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ pdf2json (1.1.7 → 1.3.0) · Repo

Release Notes

1.3.0

Biggest refactoring since v1.x, performance improvements, thorough exception handling, full metadata support and more bug fixes. Breaking changes are in README.md

1.2.5

Better error handling. README updates.

1.2.4

bug fixes and security updates

1.2.1

dependency version bump

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 17 commits:

• catch and handle canvas exceptions
• make sure only one error event raised when exception thrown, and process exits with code 0
• add testingWithTable.pdf for issue 242
• refactor pdffields and pdfcanvas with es6 class
• refactor anno, fill, image, line and unit with es6 class
• update README for v1.3.o
• 1. remove formImage and Width; 2. add the use new stream events, readable/data 3. add page level stream control in ParserStream
• update README for major refactoring v1.3.0
• add Readable stream like events, like readable, data, error to PDF.js
• include full metadata in parsed data
• refactor pdf.js with es6 class
• refactor lib/p2jcmd.js with es6 class
• Merge remote-tracking branch 'origin/master' into es6class
• Prevent `Cannot read property 'vertical' of undefined`
• add lib/parserstream to centralize stream utils
• refactor pdfparser.js with es6 class and stream
• bump dependency versions

---

👉 No CI detected

You don't seem to have any Continuous Integration service set up!

Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.

This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:

• Circle CI, Semaphore and Travis-CI are all excellent options.
• If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github.
• If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with depfu/.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

[depfu]

Closed in favor of #42.