Casey Watson
Casey Watson
This is useful for verifying that the provider is available: `:call health#provider#check()` ``` ## Clipboard (optional) - OK: Clipboard tool found: pbcopy ## Python 2 provider (optional) - INFO: `g:python_host_prog`...
I've gathered the following requirements for using the node provider: * `npm install -g yarn` (not sure why yarn is required by the health check, if it really is a...
Agreed. This is a very common use case to scroll to the bottom to see the build result.
Consider something like [keytar](https://www.npmjs.com/package/keytar) for cross-platform keychain access.
@jcalfee 's test will pass with warnings on OSX (with a case-insensitive file system) The test fails when run on a case-sensitive file system. OSX ``` webpack --entry ./bb.js bb_out.js...
For webpack it's common to install dependencies through npm or possibly bower. Renaming the files might not be feasible in the case where the dependencies are managed. I think the...
I may be wrong about people using bower with webpack and browserify. Common case is npm installs bytebuffer and it's node_modules.
Proposed fix here: https://github.com/dcodeIO/ByteBuffer.js/pull/59
A resolve alias seems to be a good solution if you just need to use ByteBuffer and Long (but not protobufjs). ``` // webpack config.js resolve: { alias: { "Long":...
This is much better than having to use the script-loader to include protobufjs or bytebuffer. The script-loader approach can't set globals in IE10.