Update pdf2json: 1.1.7 → 1.2.4 (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.2.4) · Repo

Release Notes

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 22 commits:

• publish @1.2.4
• Merge pull request #241 from h3ku/master
• Merge pull request #238 from cmmcneill/fix_xobject_infinite_loop
• Update xmldom to 0.7.1
• Safer paintFormXObjectEnd
• Merge pull request #239 from cmmcneill/allow_long_name_tokens
• Merge pull request #237 from dumdam/patch-2
• Warn instead of error when name token longer than spec
• Fixed infinite loop with paintFormXObjectEnd
• Fix "Callback must be a function" error
• publish v1.2.3
• dependency updates
• release v1.2.2
• update package.json, prep for release
• Merge pull request #215 from cmmcneill/dropdown_options_fix
• Merge pull request #225 from AirIntServices/master
• Merge pull request #228 from mojoaxel/patch-1
• Merge pull request #230 from varney/get-rid-of-optimist
• Merge pull request #231 from modesty/dependabot/npm_and_yarn/lodash-4.17.21
• build(deps): bump lodash from 4.17.20 to 4.17.21
• Replace optimist with yargs
• fix license type to be valid spdx identifier

---

👉 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 #38.