Broken if not loaded using webpack due to `require.context` #159

alexmingoia · 2015-12-06T20:30:11Z

require.context is not available unless transpiled using webpack. This breaks any module that depends on ipfs-api and uses another loader such as browserify, such as webui.

Webpack's `require.context` is transpiled only if ipfs-api is loaded or bundled using webpack. This broke modules that require ipfs-api and use browserify or other bundlers. Fixes ipfs-inactive#159

dignifiedquire · 2015-12-06T20:31:24Z

If you don't want to transpile using webpack, why not just load the prebuilt files in dist?

daviddias · 2015-12-06T21:20:17Z

@dignifiedquire being browserify compatible, or in another words, maintaining that available for the developers that have been using js-ipfs-api with browserify from the beginning, it is kind of important and nice to have.

Seems like @alexmingoia already fixed it #160

alexmingoia mentioned this issue Dec 6, 2015

Replace require.context with individual requires. #160

Merged

daviddias closed this as completed in #160 Dec 6, 2015

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Broken if not loaded using webpack due to `require.context` #159

Broken if not loaded using webpack due to `require.context` #159

alexmingoia commented Dec 6, 2015

dignifiedquire commented Dec 6, 2015

daviddias commented Dec 6, 2015

Broken if not loaded using webpack due to require.context #159

Broken if not loaded using webpack due to require.context #159

Comments

alexmingoia commented Dec 6, 2015

dignifiedquire commented Dec 6, 2015

daviddias commented Dec 6, 2015

Broken if not loaded using webpack due to `require.context` #159

Broken if not loaded using webpack due to `require.context` #159