browserify Profile
browserify

@browserify

Followers
5K
Following
37
Media
0
Statuses
276

require('modules') in the browser. project status feed.

Joined January 2014
Don't wanna be here? Send us removal request.
@browserify
browserify
5 years
browserify 17 is out! As usual, the breaking changes are mostly due to core module shims matching upstream changes in Node.js. New features: - util.promisify! - EventEmitter#off! - events.once! - stream.pipeline! https://t.co/xKB43F0oU7
Tweet card summary image
github.com
Upgrade events to v3.x. EventEmitter instances now have an off() method. require('events').once can be used to react to an event being emitted with async/await syntax. (#1839) Upgrade path-...
2
6
24
@browserify
browserify
7 years
commonjs-assert 1.5.0 is out! This package is used in browserify when you do `require('assert')`. In the first release in almost 2 years, @lukechilds added the `assert.strict` API from Node.js.
Tweet card summary image
github.com
Add strict mode APIs. (@lukechilds in #41)
0
0
5
@goto_bus_stop
Renée
7 years
the latest version of the @browserify bundle flattener `browser-pack-flat` now detects modules that are conditionally or lazily `require()`d, fixing issues with some more complex CommonJS patterns. still with minimal runtime for most modules! (←in →out) https://t.co/BtogMxZgG8
1
5
11
@browserify
browserify
7 years
If you are getting static-eval security warnings through brfs, glslify, or similar transforms, your code is not vulnerable. The security warning only applies if you are passing untrusted user input into these transforms. To clear the warning, update to static-module@^3.0.1.
0
1
6
@matteocollina
Matteo Collina
7 years
.@npmjs just declared half of the browserify ecosystem vulnerable to a HIGH security vulnerability that’s not a vulnerability in this case. If you are using @browserify, don’t panic.
3
5
10
@browserify
browserify
7 years
https://t.co/eK1IPdiOfh has moved to a new server! it should be more stable going forward.
2
1
6
@browserify
browserify
8 years
`brfs` 1.5.0 brings source mapping when doing `browserify --debug`:
Tweet card summary image
github.com
the brfs transform now generates source maps in --debug mode.
2
3
12
@browserify
browserify
8 years
brand new: browserify@16.1.0, with `--bare` and `--node` equivalents for the Node API—
0
5
12
@browserify
browserify
8 years
browserify 16.0.0 updates `events` to match the Node 8 API; adds --preserve-symlinks flag from Node 6.3; fixes issues resolving transforms installed with `pnpm`. check it out → https://t.co/UJpjevhMgO
0
6
8
@browserify
browserify
8 years
watchify 3.10.0 is released and now uses browserify v15 ✨
0
0
2
@4kilobytes
choo
8 years
Sheetify v7.1.0 has been released. Now includes better support for already-compiled code, and an upgrade to our file watcher →
Tweet card summary image
github.com
:sparkles: Modular CSS bundler for browserify. Contribute to stackcss/sheetify development by creating an account on GitHub.
0
2
9
@goto_bus_stop
Renée
8 years
bankai 9.1, now with: faster boot using v8-compile-cache; fix for dependencies shipping their own .babelrc; only copying assets when they were changed (good for `dat share`ing your site!)
Tweet card summary image
github.com
:station: - friendly web compiler. Contribute to choojs/bankai development by creating an account on GitHub.
1
4
17
@goto_bus_stop
Renée
8 years
selectively run browserify transforms using globs or a filter function, w the node api or the cli: https://t.co/62OCqIV1Dt
Tweet card summary image
github.com
selectively run browserify transforms using globs or a filter function - goto-bus-stop/tfilter
0
1
5
@browserify
browserify
8 years
browserify inside™
@4kilobytes
choo
8 years
It's here: Bankai v9, the friendly web compiler →
0
2
5
@browserify
browserify
8 years
🧙
0
2
13
@browserify
browserify
9 years
14.3.0 updates https-browserify to 1.0.0, which matches node.js behavior more closely
0
4
4