Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
8.1.3
->17.0.0
Release Notes
browserify/browserify
v17.0.0
Compare Source
off()
method.require('events').once
can be used to react to an event being emitted withasync
/await
syntax. (#1839)require('stream')
now matches the Node.js 10+ API. (#1970)util.promisify
andutil.callbackify
are finally available by default in browserify. (#1844).json
files will now fail to bundle. (#1700)v16.5.2
Compare Source
Upgrade browser-resolve to v2.
https://github.com/browserify/browserify/pull/1973
v16.5.1
Compare Source
Remove deprecated
mkdirp
version in favour ofmkdirp-classic
.browserify/browserify@00c913f
Pin dependencies for Node.js 0.8 support.
https://github.com/browserify/browserify/pull/1939
v16.5.0
Compare Source
Support custom name for
"browser"
field resolution inpackage.json
using thebrowserField
option.https://github.com/browserify/browserify/pull/1918
v16.4.0
Compare Source
Upgrade stream-http to v3. This version drops support for IE10 and below.
https://github.com/browserify/browserify/pull/1916
v16.3.0
Compare Source
add empty stub for the
http2
builtin module.https://github.com/browserify/browserify/pull/1913
update license text to remove references to code that is no longer included.
https://github.com/browserify/browserify/pull/1906
add more tests for folder resolution.
https://github.com/browserify/browserify/pull/1139
v16.2.3
Compare Source
add empty stub for the
inspector
builtin module.https://github.com/browserify/browserify/pull/1854
change the "browser" field link to the browser-field-spec repo instead of the old gist.
https://github.com/browserify/browserify/pull/1845
v16.2.2
Compare Source
Remove some extraneous files from the published package.
v16.2.1
Compare Source
Fix relative
--external
paths on Windows.https://github.com/browserify/browserify/pull/1704
Fix tests to work on Windows, and add Appveyor CI for Windows testing.
https://github.com/browserify/browserify/pull/1819
v16.2.0
Compare Source
update the browser versions of
vm-browserify
andstring_decoder
.string_decoder
updates to the Node 8+ API.vm-browserify
replaces an unlicensed dependency by an MIT one.https://github.com/browserify/browserify/pull/1829
v16.1.1
Compare Source
add empty stub for the
perf_hooks
builtin module.https://github.com/browserify/browserify/pull/1815
v16.1.0
Compare Source
add
bare
andnode
options to the API, same as the--bare
and--node
CLI arguments.https://github.com/browserify/browserify/pull/1804
v16.0.0
Compare Source
add
--preserve-symlinks
option from Node 6.3https://github.com/browserify/browserify/pull/1742
https://github.com/browserify/browserify/pull/1801
update the browser version of
events
to 2.0.0—this version adds methods likeprependListener
that were introduced in recent node versions, but it is also twice the size of events v1.x (2KB instead of 1KB).https://github.com/browserify/browserify/pull/1803
Dynamically calculate
__dirname
and__filename
when--node
is passedhttps://github.com/browserify/browserify/pull/1725
upgrade module-deps, see https://github.com/browserify/module-deps/releases/tag/v6.0.0
browserify/browserify@e5e1ec8
v15.2.0
Compare Source
create parent directories if they do not exist when
--outfile /x/y/z/bundle.js
is usedhttps://github.com/browserify/browserify/pull/995
add regression test for object rest spread syntax
https://github.com/browserify/browserify/pull/1798
v15.1.0
Compare Source
restore support for node
< 4.0
until we can decide on a support schedulev15.0.0
Compare Source
fixed repository url in package.json.
browserify/browserify@5ec19ee
update
module-deps
to 5.0.0, which enables requiring modules in backtick-enclosed strings.https://github.com/browserify/browserify/pull/1785
dropped testing in node 0.10 and 0.12, set supported node versions to
>=4
https://github.com/browserify/browserify/pull/1743
https://github.com/browserify/browserify/pull/1793
add support for passing arrays to the
exclude
andignore
methods.https://github.com/browserify/browserify/pull/1769
v14.5.0
Compare Source
update
os-browserify
to 0.3.0, which adds a shim for node.js'sos.homedir
method.https://github.com/browserify/browserify/pull/1767
update
browserify-zlib
to 0.2.0, which adds support for dictionaries.https://github.com/browserify/browserify/pull/1733
v14.4.0
Compare Source
update
string_decoder
to 1.0.0, which matches the latest node.js behavior more closely.https://github.com/substack/node-browserify/pull/1714
v14.3.0
Compare Source
update
https-browserify
to 1.0.0, which matches node.js behavior more closely.https.request
orhttps.get
https.request
andhttps.get
https://github.com/substack/node-browserify/pull/1710
v14.2.0
Compare Source
adds a --transform-key flag to the command-line tool
https://github.com/substack/node-browserify/pull/1709
v14.1.0
Compare Source
writes to a temp outfile until success
Previously, browserify would overwrite output files when an error occurs.
https://github.com/substack/node-browserify/pull/1673
https://github.com/substack/node-browserify/issues/899
v14.0.0
Compare Source
Updates the version of the buffer package, which drops support for IE8-10.
buffer v5 removes the
Object
implementation and relies on a single,fast Typed Array (
Uint8Array
) implementation, greatly simplifying themaintanence of the buffer package.
If IE8-10 support is critical to your web app, you can continue to rely on
browserify v13, or see the PR for other workarounds.
https://github.com/substack/node-browserify/pull/1678
v13.3.0
Compare Source
updates the version for the assert package
https://github.com/substack/node-browserify/pull/1611
v13.2.0
Compare Source
allow configuring transformKey from module-deps
https://github.com/substack/node-browserify/pull/1670
v13.1.1
Compare Source
boost performance by memoizing calls to path.relative()
https://github.com/substack/node-browserify/pull/1544
v13.1.0
Compare Source
exposes
opts.dedupe
and--no-deupe
to optionally turn off deduping behavior:#1581
v13.0.1
Compare Source
Internal
#1552, #1555: Use native
Array.isArray
and dropisarray
dep. (@kt3k)v13.0.0
Compare Source
This release bumps the
buffer
dependencyto v4, which has one possible breaking change:
buffer.toArrayBuffer()
method onBuffer
instances has been removed.(This is probably not a problem for 99.9% of users.)
This API was added in node v0.11.8 and
removed before v0.12 was released.
It was added to browserify's
buffer
implementation but was never removed when v0.12was released.
buffer
v4 removes it so we have full parity with node.js.Going forward, to get an
ArrayBuffer
from a node.js-styleBuffer
, users shouldjust use
buffer.buffer
. This works becauseBuffer
is a subclass ofUint8Array
in both the browser and node.js (since v3).
On the plus side, this release also includes:
buffer
thatincrease the speed of some buffer
methods by as much as 30%!
v12.0.2
Compare Source
normalizes module paths on windows to consistently use
/
https://github.com/substack/node-browserify/pull/1424#issuecomment-170143099
v12.0.1
Compare Source
adds the previously failing tests and a small change necessary for transforms to
be applied properly for symlinked packages
https://github.com/substack/node-browserify/pull/1392
v12.0.0
Compare Source
Node support changes: now testing against the latest node (currently 4.2.1).
node 0.8 is no longer supported, and iojs isn't actively tested.
Stream3 everywhere! Everything has been updated to use streams3.
Sourcemaps charset now uses an
=
instead of a:
. This fixes certain issueswith Chinese characters in sourcemaps. See #753.
module-deps has been updated to fix root transforms on symlinked modules. See
https://github.com/substack/module-deps/pull/99.
stream-http, the module that provides
http
support, dropped IE8 support. Ifyou depend on this, see https://github.com/jhiesey/stream-http#ie8-note.
Removed
builtins
andcommondir
– both unused dependencies.v11.2.0
Compare Source
When
bundleExternal
is set tofalse
,process
andbuffer
are now correctly excluded. Also, using--igv
via the CLI now works. That also means that--bare
and--node
actually insert__filename
and__dirname
.https://github.com/substack/node-browserify/pull/1361
v11.1.0
Compare Source
adds a
'.'
to extensions if it wasn't addedhttps://github.com/substack/node-browserify/pull/1380
v11.0.1
Compare Source
The callback form of bundle() uses the returned output stream instead of the
pipeline so that the
'end'
event will fire on the bundle instance.https://github.com/substack/watchify/pull/249#issuecomment-126061169
v11.0.0
Compare Source
streams3
The
readable-stream
dependency was updated to^2.0.0
. This package is inserted into bundles asrequire('stream')
. Bundles will now get the latest streams implementation from io.js/node.js core, instead of an old version from node.js 0.11.x. Go forth and stream ALL THE DATA without fear!shiny new HTTP package
John Hiesey rewrote the http-browserify package
to create stream-http, an implemention of
http
that supports streaming in modern browsers. Before v11.0.0, in most situations when you usedhttp.get
orhttp.request
, the entire request would buffer in memory until the download was complete, and a single'data'
event was emitted with the entire response as a string.stream-http
uses the Fetch API and various browser-specific XHR extensions to make binary streaming http requests work in as many browsers as possible.The following browsers support true streaming, where only a small amount of the request has to be held in memory at once:
fetch
api)moz-chunked-arraybuffer
responseType with XHR)The following browsers support pseudo-streaming, where the data is available before the request finishes, but the entire response must be held in memory:
Older browsers will work, without streaming support. There is no support for IE6 or IE7.
Compared to
http-browserify
, it is not necessary to setoptions.responseType
. TheresponseType
property of the XHR object will be set automatically depending on what features are detected in the browser (although seeoptions.mode
in the readme to see how you can optimize this choice manually).The
response
is a streams3 stream, so all data is passed asBuffer
s, unlike the variable types provided by the'data'
event inhttp-browserify
. This behavior tries to mimic the node corehttp
module as closely as possible.If you're brave, go ahead and give v11.0.0 a try today!
v10.2.6
Compare Source
uses the non-sync version of fs.realpath
v10.2.5
Compare Source
fixes an issue with symlinked files executing multiple times
https://github.com/substack/node-browserify/issues/1063
https://github.com/substack/node-browserify/pull/1318
v10.2.4
Compare Source
fixes requiring an entry from another entry
remove unused dep "deep-equal" and unused file "lib/_exclude.js"
https://github.com/substack/node-browserify/pull/1268
v10.2.3
Compare Source
fixes an errant space in the
--no-browser-field
flag aliasthat kept it from working
https://github.com/substack/node-browserify/issues/1286
v10.2.1
Compare Source
housekeeping - removed unused code
https://github.com/substack/node-browserify/pull/1273
v10.2.0
Compare Source
remove unnecessary "isDedupe" json check. this was a hack-fix for watchify <=2.4.
https://github.com/substack/node-browserify/pull/1244
fixes for the "noParse" path matcher.
https://github.com/substack/node-browserify/pull/1257
add syntax check cache. this speeds up rebuilds (like when using watchify).
https://github.com/substack/node-browserify/pull/1253
update to browser-pack@^5.0.0 - includes several fixes related to source maps.
https://github.com/substack/node-browserify/pull/1259
v10.1.3
Compare Source
Replace jsonstream with JSONStream
https://github.com/substack/node-browserify/pull/1252
v10.1.2
Compare Source
Replace JSONStream with jsonstream
Update deps to avoid jsonstream npm case problems
https://github.com/substack/node-browserify/pull/1247
browserify/browserify@1ca71e23
v10.1.1
Compare Source
ensures that entry paths are always full paths
https://github.com/substack/node-browserify/pull/1248
v10.1.0
Compare Source
adds
--no-browser-field
andopts.browserField = false
behavior to turn offthe package.json browser field. This is useful if you want to make a bundle with
a target of node or some environment with shimmed node primitives.
A new alias
--node
sets--no-browser-field
and--bare
.https://github.com/substack/node-browserify/pull/1240
v10.0.0
Compare Source
Possibly Breaking Change
The ‘process’ dependency was updated to ~0.11.0, this module is inserted into bundles as the ‘process’ global/dependency.
Previously, an unhandled error thrown in a ‘process.nextTick’ task would prevent any subsequent tasks from running, forever.
The task queue now recovers from this condition, but may do so on a future browser tick.
As part of this update, ‘process.nextTick’ now accepts variadic arguments, passed to the task, added to io.js in 1.8.1.
Other changes
v9.0.8
Compare Source
makes
.require({ expose: 'name' })
andrequire('name')
work at the same timehttps://github.com/substack/node-browserify/issues/850
https://github.com/substack/node-browserify/pull/1202
v9.0.7
Compare Source
fixes an issue with catching error events on the b.bundle() stream
https://github.com/substack/node-browserify/issues/1194
https://github.com/substack/node-browserify/pull/1195
v9.0.6
Compare Source
republishing 9.0.5 in an attempt to satisfy npm.
v9.0.5
Compare Source
sets the stream returned by bundle() to be readable-only
https://github.com/substack/node-browserify/pull/1187#issuecomment-89044008
v9.0.4
Compare Source
handles the colon better for drive paths and improves the test suite for windows
users
https://github.com/substack/node-browserify/pull/1182
https://github.com/substack/node-browserify/pull/1183
v9.0.3
Compare Source
fixes a problem with deduping for json files.
This caused problems for running bundle() multiple times on the same instance
with caching turned on, which people reported encountering using watchify.
https://github.com/substack/node-browserify/issues/1101
https://github.com/substack/watchify/issues/143
v9.0.2
Compare Source
fixes a bug where transforms in
opts.transform
were getting run twicehttps://github.com/substack/node-browserify/issues/1124
https://github.com/substack/node-browserify/pull/1128
v9.0.1
Compare Source
fixes exposed files persisting across bundles
https://github.com/substack/node-browserify/pull/1030
v9.0.0
Compare Source
updates browser-pack which uses umd 3.0.0.
This sligtly changes how
--standalone $name
works.https://github.com/substack/browser-pack/pull/49
https://github.com/substack/node-browserify/pull/1105
Also some tidying up around handling expose that module-deps can do now:
https://github.com/substack/node-browserify/pull/1077
and some fixes to regressions involving the
'package'
event:https://github.com/substack/node-resolve/issues/69
Upstream changes in resolve/browser-resolve mean that
require('foo/bar')
worksbetter with the package.json browser field. You can do something like:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.