Update pkg: 4.4.0 → 4.5.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?

✳️ pkg (4.4.0 → 4.5.0) · Repo

Release Notes

4.5.0

• Branding change (#939)
• Update badges in README (#949)
• update tests test for node 14 CI (#977)
• Bump lodash from 4.17.15 to 4.17.19 (#945)
• Added environment var section on Readme (#684)
• Add missing stat.isSocket (#720)
• Fix configuration for node-notifier (#1021)
• Add support for Node native addons (#837)
• docs: MAKE_JOB_COUNT and PKG_IGNORE_TAG env var (#1053)
• Bugfix for fs.readdir(), fs.readdirSync() (#992)
• Replace deprecated assert.equal and assert.deepEqual. (#1063)
• Update ZEIT to Vercel in package.json. (#1064)
• Add cross-platform support for dot-node files. (#1066)

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

Commits

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

• 4.5.0
• Add cross-platform support for dot-node files. (#1066)
• Update ZEIT to Vercel in package.json. (#1064)
• Replace deprecated `assert.equal` and `assert.deepEqual`. (#1063)
• Bugfix for fs.readdir(), fs.readdirSync() (#992)
• docs: MAKE_JOB_COUNT and PKG_IGNORE_TAG env var (#1053)
• Add support for Node native addons (#837)
• Fix configuration for node-notifier (#1021)
• Add missing stat.isSocket (#720)
• Added environment var section on Readme (#684)
• Bump lodash from 4.17.15 to 4.17.19 (#945)
• update tests test for node 14 CI (#977)
• Update badges in README (#949)
• Branding change (#939)
• 4.4.9
• bump pkg-fetch
• decouple node14 from node12 in test-50-fs-runtime-layer-2
• bump node versions in CI
• move dictionary-related work to readDictionary
• Added support for user-defined pkg config for 3rd party dependencies (#868)
• 4.4.8
• add testing node 14. remove testing node 8
• bump pkg-fetch. adds node 14
• feat: support for classPrivateProperties (#891)
• 4.4.7
• uppercaseDriveLetter is not needed in posix normalizePath
• fix URL file paths for win32
• make isRootPath support directory path as buffer
• consider file path as Buffer and as URL. fixes #886
• fix tests runner and test-50-fs-runtime-layer-2
• 4.4.6
• reset yarn.lock, bump kind-of to 6.0.3
• pin fs-extra temporarily. fixes https://github.com/zeit/pkg/issues/883
• 4.4.5
• bump dependencies
• dictionary for compressjs. fixes #827
• update dictionary for node-forge. addresses #791
• Bump minimist from 1.2.0 to 1.2.2 (#867)
• Bump acorn from 7.1.0 to 7.1.1 (#866)
• 4.4.4
• Fix for #808 (#856)
• Add support for native bigint parsing (#771)
• Load image over HTTPs (#853)
• Fixed grammar and sentence structure (#797)
• readdir-options (#854)
• 4.4.3
• bump some dependencies
• test for 460ff6c
• fix "inside node_modules calling itself via package name" case
• legend to clarify what are %1 and %2
• test for regression fix
• fix a regression
• update leveldown dictionary. addresses #758 and #825
• restore test for opn
• preserve the dictionary for opn
• rename opn to open. fixes #824
• update zeromq dictionary and test
• Add ZEIT Now Disclaimer (#823)
• 4.4.2
• don't parse files that are unlikely javascript. fixes #75 and #317
• describe how to make 'microjob' work. fixes #811
• take natives from 'resolve' and adjust them. fixes #807
• Release 4.4.1
• adopt new version of 'resolve' dependency
• fixes for globby. test fixes. bump pkg-fetch
• update dependencies
• test: test-50-bakery-4 for baking non-v8 options
• tolerate underscore in bakes excluded from fabricator

---

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