Consider using static require dependencies

There is an issue when using the package with https://github.com/jspm (sytemjs) https://github.com/jspm/registry/issues/221

this code uses dynamic requires https://github.com/netroy/image-size/blob/master/lib/index.js#L6-L15

and https://github.com/systemjs/systemjs can not handle it.

Actually it is importaint as image-size is used with css precompilers (such as LESS) and they have to be used in systemjs-builder worflow.

Would you consider chanding requires to static paths? Or addings static deps declarations in the beginning of the file?

[pawlufelice]

This is a problem for me too!! I have browserify on an express app and the dynamic requires just to not get bundled, resulting in module not found. Please have them changed to static. Thanks

[danielweck]

Indeed, Browserify (which ; by the way ; is not only used for client-side bundling, but can also be used to package server-side code, e.g. in Electron) fails to fulfill the dynamic require() calls, for instance: https://github.com/image-size/image-size/blob/a71d6372c95e79efa0b349153a8525381aab0e5c/lib/index.js#L9-L14 (from the types list defined at https://github.com/image-size/image-size/blob/master/lib/types.js )

The current workaround is to add explicit requires for each “type” using a hard-coded path. This is actually standard practice in several CommonJS libs, to ensure Browserify (and others) compatibility.