cash: Does not work in IE11

I’m closing this then. It will be helpful to other users if you guys shared a webpack configuration that handles the transpilation properly.

I’ve build a thing for checking that cash can be properly imported under the most common environments (attached below, it may come in handy in the future).

This issue has ben fixed by https://github.com/kenwheeler/cash/pull/291. Basically the only problem was when importing cash via require and when bundling that with webpack. I’m not quite sure why that was happening to be honest.

The bottom line is that importing cash should now work everywhere, and when explicitly importing cash it won’t pollute the global namespace. If you want $ to be globally available just expose it yourself: window.$ = $.

New release coming soon (I want to take care of a few other issues first).

cash-dom-import-test.zip

@fabiospampinato I’d like to reopen this. Webpack relies on package.json of various packages to be able to resolve the module. It has a sensible default for web target: browser followed by module and finally main.

cash advertises support for “modern browsers (IE10+)” and its package.json contains just main and module.

"main": "./dist/cash.js",
"module": "./dist/cash.esm.js"

The proposed solution (@makotot) suggests changing the Webpack configuration for every package to look at main field first and module field next, which would work for cash, given the contents of its package.json file.

However, adding a browser field to point to dist/cash.js would work just as well, and would work with no global changes required on Webpack configuration.

"browser": "./dist/cash.js",
"main": "./dist/cash.js",
"module": "./dist/cash.esm.js"

Using resolve.mainFields like mainfilelds: ["main", "module"] may be the optimal solution for this issue. ref: https://github.com/webpack/webpack/issues/1979

@fabiospampinatoThanks, I understand. I’m grateful for your support.