stevenvachon/universal-url

WHATWG URL for Node & Browser.

universal-url

WHATWG URL for Node & Browser.

• For Node.js versions >= 8, the native implementation will be used.
• For Node.js versions < 8, a shim will be used.
• For web browsers without a native implementation, the same shim will be used.

Installation

Node.js >= 6 is required. To install, type this at the command line:

npm install universal-url

Usage

const {URL, URLSearchParams} = require('universal-url');

const url = new URL('http://domain/');
const params = new URLSearchParams('?param=value');

Global shim:

require('universal-url').shim();

const url = new URL('http://domain/');
const params = new URLSearchParams('?param=value');

Browserify/etc

The bundled file size of this library can be large for a web browser. If this is a problem, try using universal-url-lite in your build as an alias for this module.

universal-url's Issues

Typescript support?

Any intention to support Typescript typings?

An in-range update of mocha is breaking the build 🚨

Version 5.2.0 of mocha was just published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	5.1.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

mocha is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Release Notes

v5.2.0

5.2.0 / 2018-05-18

🎉 Enhancements

• #3375: Add support for comments in mocha.opts (@plroebuck)

🐛 Fixes

• #3346: Exit correctly from before hooks when using --bail (@outsideris)

📖 Documentation

• #3328: Mocha-flavored API docs! (@Munter)

🔩 Other

• #3330: Use Buffer.from() (@harrysarson)
• #3295: Remove redundant folder (@DavNej)
• #3356: Refactoring (@plroebuck)

Commits

The new version differs by 30 commits.

• 5bd33a0 Release v5.2.0
• 0a5604f reformat missed files
• 7c8f551 ensure scripts/*.js gets prettiered
• d8ea2ba update CHANGELOG.md for v5.2.0 [ci skip]
• 7203ed7 update all dependencies
• fb5393b migrate Mocha's tests to Unexpected assertion library (#3343)
• fae9af2 docs(docs/index.md): Update "mocha.opts" documentation
• 9d9e6c6 feat(bin/options.js): Add support for comment lines in "mocha.opts"
• e0306ff fix busted lint-staged config
• f2be6d4 Annotate when exceptions are caught but ignored; closes #3354 (#3356)
• 889e681 remove dead code in bin/_mocha
• 8712b95 fix(ocd): re-order Node.js tests in .travis.yml (descending)
• 3ab0e7e fix to exit correctly when using bail flag
• d87b12e add Node.js v10 to build; fix win32 issues (#3350)
• b392af5 update package-lock.json for npm@6 [ci skip]

There are 30 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of whatwg-url is breaking the build 🚨

Version 6.3.0 of whatwg-url just got published.

Branch	Build failing 🚨
Dependency	whatwg-url
Current Version	6.2.1
Type	dependency

This version is covered by your current version range and after updating it in your project the build failed.

whatwg-url is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

---

Commits

The new version differs by 2 commits.

• 18d92e9 6.3.0
• b53b6e8 Spec update: Windows drive letter quirk in the file slash state

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of puppeteer is breaking the build 🚨

The devDependency puppeteer was updated from 1.17.0 to 1.18.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v1.18.0

Big Changes

• Chromium 77.0.3827.0 (r669486)

API changes

No API changes.

Bug Fixes

• #2755 - blurry canvas if deviceScaleFactor > 1
• #4442 - Some pages not fully loading when setRequestInterception set to true
• #4449 - goto takes an increasing amount of time.
• #4454 - Intercepted requests won't return with some status codes
• #4536 - Dangling promises / unhandled rejection due to missing await keywords in mouse.click
• #4537 - Page.select throwing error when select change page
• #4543 - Cannot retrieve content of pages that are >100MB.
• #4545 - page.queryObjects doesn't work as expected
• #4556 - https-agent makes http PUPPETEER_DOWNLOAD_HOST download fail
• #4559 - non matching contribution rules makes PR have errors
• #4563 - Too large write data is pending: size=725124416, max_buffer_size=268435456
• #4568 - A3 paper size is incorrect

Raw notes

45873ea - feat(chromium): roll Chromium to r669486 (#4591)
955e7cb - feat(page): move page.pdf to protocol streams (#4587)
6c2007f - docs(README.md): fix spelling of Stack Overflow (#4590)
62733a2 - fix(connection): bump websocket max received message size to 256Mb (#4571)
5087962 - feat(chromium): roll Chromium to r668716 (#4581)
6860d73 - fix(network): align HTTP status codes with IANA (#4567)
7922641 - fix(page): fix A2 and A3 format size (#4569)
65b7e8e - docs(api.md): add notes on race condition in page.setViewport (#4319)
8df0b3e - fix(network): allow fulfilling requests with status code 422 (#4566)
b2f9490 - fix(eval): be able to throw protocol like errors (#4551)
6a50888 - fix(firefox): fix missing awaits in mouse.click (#4561)
e1432cc - docs(contributing): update commit message example (#4560)
dd6fcfe - fix(page): fix missing awaits in mouse.click (#4541)
7faf1c9 - fix(BrowserFetcher): fix httpRequest when using proxy against http HOST (#4558)
4bcdfc9 - docs(api.md): clarify frame/page.goto()'s handling of HTTP error statuses (#4553)
aca99cd - docs(troubleshooting): add missing double quotes (#4548)
90df69c - fix(page): do evaluations with one roundtrip (#4539)
7e19846 - feat(chromium): roll Chromium to r666595 (#4530)
f79d0a3 - fix: try running without --disable-gpu on windows (#4523)
15804d1 - test: remove debug console.log (#4522)
78d5106 - feat(chromium): roll Chromium to r665405 (#4516)
f52738e - docs(api.md): clarify on HTTP error responses (#4507)
94ff4de - docs(troubleshooting): fix comment (#4512)
ac611ba - fix(helper): fix Helper.installAsyncStackHooks method (#4478)
d221c02 - test: add test to verify fetching of dataURL requests (#4233)
015e330 - test: add oopif tests (#4495)
111350c - docs(troubleshooting.md): update Alpine instructions (#4494)
084cf02 - chore: bump version to v1.17.0-post (#4468)

Commits

The new version differs by 29 commits.

• c96454d chore: mark version v1.18.0 (#4606)
• 45873ea feat(chromium): roll Chromium to r669486 (#4591)
• 955e7cb feat(page): move page.pdf to protocol streams (#4587)
• 6c2007f docs(README.md): fix spelling of Stack Overflow (#4590)
• 62733a2 fix(connection): bump websocket max received message size to 256Mb (#4571)
• 5087962 feat(chromium): roll Chromium to r668716 (#4581)
• 6860d73 fix(network): align HTTP status codes with IANA (#4567)
• 7922641 fix(page): fix A2 and A3 format size (#4569)
• 65b7e8e docs(api.md): add notes on race condition in page.setViewport (#4319)
• 8df0b3e fix(network): allow fulfilling requests with status code 422 (#4566)
• b2f9490 fix(eval): be able to throw protocol like errors (#4551)
• 6a50888 fix(firefox): fix missing awaits in mouse.click (#4561)
• e1432cc docs(contributing): update commit message example (#4560)
• dd6fcfe fix(page): fix missing awaits in mouse.click (#4541)
• 7faf1c9 fix(BrowserFetcher): fix httpRequest when using proxy against http HOST (#4558)

There are 29 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.0 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.3.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

v3.4.0

Mocha is now moving to a quicker release schedule: when non-breaking changes are merged, a release should happen that week.

This week's highlights:

• allowUncaught added to commandline as --allow-uncaught (and bugfixed)
• warning-related Node flags

🎉 Enhancements

• #2793, #2697: add --allowUncaught to Node.js (@lrowe)
• #2733: Add --no-warnings and --trace-warnings flags (@sonicdoe)

🐛 Fixes

• #2793, #2697: fix broken allowUncaught (@lrowe)

🔩 Other

• #2778: Add license report and scan status (@xizhao)
• #2794: no special case for macOS running Karma locally (@boneskull)
• #2795: reverts use of semistandard directly ([#2648]) (@boneskull)

Commits

The new version differs by 9 commits0.

• 7554b31 Add Changelog for v3.4.0
• 9f7f7ed Add --trace-warnings flag
• 92561c8 Add --no-warnings flag
• ceee976 lint test/integration/fixtures/simple-reporter.js
• dcfc094 Revert "use semistandard directly"
• 93392dd no special case for macOS running Karma locally
• 4d1d91d --allow-uncaught cli option
• fb1e083 fix allowUncaught in browser
• 4ed3fc5 Add license report and scan status

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of puppeteer is breaking the build 🚨

Version 1.6.2 of puppeteer was just published.

Branch	Build failing 🚨
Dependency	puppeteer
Current Version	1.6.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes

v1.6.2

Big Changes

• Chromium 69.0.3494.0 (r575458)

API changes

No API changes.

Bug Fixes

• #2970 - There are some missing responses on 'page.on("response") when I invoke 'page.goto()'

Raw notes

ed52acc - chore: mark version v1.6.2
c0d8b3b - test: add test with request interception and cookies (#2988)
2f059bf - fix(NetworkManager): Remove header 'cookie' from request hash (#2954)

Commits

The new version differs by 3 commits.

• ed52acc chore: mark version v1.6.2
• c0d8b3b test: add test with request interception and cookies (#2988)
• 2f059bf fix(NetworkManager): Remove header 'cookie' from request hash (#2954)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of mocha is breaking the build 🚨

Version 3.4.1 of mocha just got published.

Branch	Build failing 🚨
Dependency	mocha
Current Version	3.4.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

• ❌ continuous-integration/travis-ci/push The Travis CI build failed Details

---

Release Notes

Ohai CRLF...

Fixed a publishing mishap with git's autocrlf settings.

Commits

The new version differs by 3 commits0.

• ac0c1c8 v3.4.1
• 64d96d3 :ship: Release v3.4.0
• 4e3252e Force rebuild of mocha.js on npm version

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

An in-range update of puppeteer is breaking the build 🚨

The devDependency puppeteer was updated from 1.10.0 to 1.11.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Release Notes for v1.11.0

Big Changes

• Chromium 72.0.3618.0 (r609904)
• page.setContent now awaits resource loading (927d0f4)

API Changes

Changed:

• page.setContent (927d0f4) now accepts waitUntil option similar to page.goto.

Bug Fixes

• #728 - Page.setContent should wait for resources to be loaded
• #3517 - Page#setViewport required options
• #3549 - Functions bound with page.exposeFunction() produce unhandled promise rejections
• #2262 - Problem with PUPPETEER_SKIP_CHROMIUM_DOWNLOAD

Raw Notes

a0cbaf3 - chore(types): lint the api docs with typescript (#3577)
fb5b080 - feat(chromium): roll Chromium to r609904 (#3587)
6656519 - test: split out dialog tests (#3586)
309cbe6 - test: split out navigation tests (#3585)
d61916b - test: split out evaluation tests (#3584)
e839189 - test: split input tests into keyboard, mouse and touchscreen (#3583)
25f4f26 - test: extract clicking tests (#3582)
a181bdd - test: split out emulation tests (#3581)
a5b1978 - test: split out waittask tests (#3580)
e5830d1 - test: split queryselector tests into separate file (#3579)
aa9fb82 - test: split screenshot tests into separate file (#3578)
a04100c - docs(troubleshooting): added link to alixaxel/chrome-aws-lambda (#3576)
927d0f4 - feat(page): support waitUntil option for page.setContent (#3557)
e2e43bc - fix(page): navigating 11 pages simultaneously should not throw warning (#3560)
86e0959 - docs(api.md): mark optional arguments in signatures (#3565)
f6bfa32 - docs(api.md): fixes #3517 (#3561)
d9d9996 - feat(chromium): roll Chromium to r608752 (#3555)
03d8746 - test(accessibility): Fix duplicated test (#3539)
95a19c7 - fix(page): dispatch errors into page (#3550)
c185eee - feat(install): support configurations in package.json (#3449)
766a951 - docs(troubleshooting): update on sandboxing (#3531)
eb7bd9d - test: setup sandbox on linux (#3530)
10a4c8c - docs(troubleshooting): modern linux sandboxing
5687343 - fix(types): fix parameters where they disagree with the api (#3525)
27ea226 - test: fix workers test (#3527)
d3f50ea - chore: update dependencies (#3526)
1d671c6 - chore(bisect): properly output bisect ranges + output styling (#3523)
576c8f8 - chore(chromium): roll Chromium to r606647 (#3522)
6693537 - chore: add utils/bisect.js to bisect chromium revisions (#3511)
59e7e8c - docs(api.md): update returned value description (#3514)
79ec7a3 - fix(types): fix return types where JSDoc and api.md disagree (#3512)
04b6ca8 - Fix dead link (#3497)
b9f2104 - test(cookies): Remove duplicated test. (#3492)
52a1030 - feat(chromium): roll Chromium to r604907 (#3488)
6b65407 - test: unflake cookie test on windows (#3489)
60a8d41 - chore: bump version to v1.10.0-post (#3483)

Commits

The new version differs by 38 commits.

• 00b1599 chore: mark version v1.11.0 (#3610)
• c09bb8f chore: pin typescript version (#3612)
• a0cbaf3 chore(types): lint the api docs with typescript (#3577)
• fb5b080 feat(chromium): roll Chromium to r609904 (#3587)
• 6656519 test: split out dialog tests (#3586)
• 309cbe6 test: split out navigation tests (#3585)
• d61916b test: split out evaluation tests (#3584)
• e839189 test: split input tests into keyboard, mouse and touchscreen (#3583)
• 25f4f26 test: extract clicking tests (#3582)
• a181bdd test: split out emulation tests (#3581)
• a5b1978 test: split out waittask tests (#3580)
• e5830d1 test: split queryselector tests into separate file (#3579)
• aa9fb82 test: split screenshot tests into separate file (#3578)
• a04100c docs(troubleshooting): added link to alixaxel/chrome-aws-lambda (#3576)
• 927d0f4 feat(page): support waitUntil option for page.setContent (#3557)

There are 38 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.4.4 to 7.4.5.

• The devDependency @babel/preset-env was updated from 7.4.4 to 7.4.5.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of puppeteer is breaking the build 🚨

Version 1.8.0 of puppeteer was just published.

Branch	Build failing 🚨
Dependency	puppeteer
Current Version	1.7.0
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

puppeteer is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes

v1.8.0

Big Changes

• Chromium 71.0.3542.0 (r588429)
• browser permissions can be managed with browserContext.overridePermissions
• request interception now works with ignorehttpserrors option

API Changes

Changed:

• PUPPETEER_CHROMIUM_REVISION and PUPPETEER_EXECUTABLE_PATH environment variables will now not only affect puppeteer installation but your scripts as well. (28d9211)
• page.goto now accepts a referer argument. (cbce839)

Added:

• browser.defaultBrowserContext (50d6c2d)
• browserContext.overridePermissions (50d6c2d)
• browserContext.clearPermissionOverrides (50d6c2d)
• page.setGeolocation (1702928)
• response.remoteAddress (1ba2b85)
• response.statusText (7f9e276)

Bug Fixes

• #317 - Response improvements
• #846 - How to catch a "Permission request" dialog event?
• #1077 - Support for geolocation mock?
• #1159 - ignoreHTTPSErrors is not working when request interception is on
• #2171 - Can I get Remote Address with puppteer？
• #2764 - Some URLs sequence makes next responses to be null
• #2925 - puppeteer@next is not autoupdated
• #3090 - Referrer should be parameter, not extra header
• #3106 - Calling a exposed function inside an evaluateOnNewDocument function does not work on Chrome 70

Raw Notes

42fde9b - chore: another attempt to fix pptr@next (#3210)
b7e922b - chore: fix puppeteer@next race condition (#3209)
f230722 - refactor: avoid dynamic requires in lib/ folder (#3208)
d54c7ed - fix(page): Page.goto should properly handle historyAPI in beforeunload (#3198)
28d9211 - feat(puppeteer): support convenience env variables (#3190)
7f9e276 - feat(network): introduce Response.statusText() (#3193)
84c2621 - refactor(network): Create Request class right away from payload (#3194)
7db4f0f - chore: preserve links to master version of API from README.md (#3197)
3364659 - docs(api.md): Added cutoff values for scale option in page.pdf function (#3201)
e07567f - docs(api.md): fix a typo (#3196)
1ba2b85 - feat(network): introduce Response.remoteAddress() (#3192)
52cf16c - refactor(network): Create Response class right away from payload (#3191)
22c0ce6 - test: cleanup newly added test for navigation referer (#3179)
2de5a42 - docs(api.md): expand on puppeteer-core vs puppeteer (#3189)
93f267b - docs(api.md): re-factor api.md heading (#3185)
cbce839 - docs(api.md): small typo (#3188)
32c0363 - feat(chromium): roll Chromium to r588429 (#3181)
464f3b4 - feat(page): Add 'referer' as a parameter to Page.goto() (#3128)
1702928 - feat(page): Introduce page.setGeolocation method (#3160)
1000997 - docs(api.md): page.hover typo (#3165)
50d6c2d - feat(browsercontext): implement BrowserContext.overridePermissions (#3159)
df459ba - feat(chromium): roll Chromium to r587164 (#3153)
bfed64f - docs(readme.md): change Megabits to Megabytes.
3d7ae2a - fix: fix null-type bugs (#3137)
d1105af - Revert "Add Puppeteer Recorder extension to docs" (#3102)
ce64ae2 - test: add test for request interception with 302 after POST (#3105)
d6eb3b4 - refactor: drop object factory from execution context (#3099)
73c43be - docs: Add Puppeteer Recorder extension to docs (#3088)
395c506 - docs(troubleshooting): add libatk-bridge2.0-0 to ubuntu dependencies (#3096)
ce78327 - feat(chromium): roll Chromium to r583214 (#3092)
b8e0d62 - docs(readme): refer to awesome-puppeteer (#3062)
3ae85e4 - docs: mention puppeteer-core (#3061)
af361c8 - chore: bump version to v1.7.0-post (#3060)

Commits

The new version differs by 34 commits.

• aeb6a99 chore: mark version v1.8.0 (#3211)
• 42fde9b chore: another attempt to fix pptr@next (#3210)
• b7e922b chore: fix puppeteer@next race condition (#3209)
• f230722 refactor: avoid dynamic requires in lib/ folder (#3208)
• d54c7ed fix(page): Page.goto should properly handle historyAPI in beforeunload (#3198)
• 28d9211 feat(puppeteer): support convenience env variables (#3190)
• 7f9e276 feat(network): introduce Response.statusText() (#3193)
• 84c2621 refactor(network): Create Request class right away from payload (#3194)
• 7db4f0f chore: preserve links to master version of API from README.md (#3197)
• 3364659 docs(api.md): Added cutoff values for scale option in page.pdf function (#3201)
• e07567f docs(api.md): fix a typo (#3196)
• 1ba2b85 feat(network): introduce Response.remoteAddress() (#3192)
• 52cf16c refactor(network): Create Response class right away from payload (#3191)
• 22c0ce6 test: cleanup newly added test for navigation referer (#3179)
• 2de5a42 docs(api.md): expand on puppeteer-core vs puppeteer (#3189)

There are 34 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.4.5 to 7.5.0.

• The devDependency @babel/preset-env was updated from 7.4.5 to 7.5.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of browserify is breaking the build 🚨

The devDependency browserify was updated from 16.2.2 to 16.2.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

browserify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

Release Notes for v16.2.3

add empty stub for the inspector builtin module.

#1854

change the "browser" field link to the browser-field-spec repo instead of the old gist.

#1845

Commits

The new version differs by 5 commits.

• cfd3af2 16.2.3
• ae01d90 Merge pull request #1854 from mohd-akram/add-inspector-builtin
• b1e61aa Add inspector builtin
• 4190ed5 Merge pull request #1845 from farzonl/patch-1
• 32d0a05 fix ReadME link.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴