version 3.1.3 is not es5 compatible because of lru-cache 5.1.1

[ayal]

version 3.1.3 bumped to lru-cache@5.1.1 which is not es5 compatible

2b63345

It might even be that lru-cache is purely meant for node:
2b63345

If that’s the case, I propose locking an older version of lru-cache until something more future-proof is done in this regard.

I can push a PR, temporarily locking in the most recent version of lru-cache that worked as expected in ES5 environments.

[kuitos]

We made this change via #72

BTW which way u used with axios-extensions?

If you used it with a script tag, we may need to change the rollup config to transpile it to compatible with es5.

If u used it with a npm way, I think u should make your babel to compile the node_modules and make your dependencies compatible with es5 after bundler build.

[ayal]

I use the package with npm.

Of course I can transpile lru-cache myself but I was under the impression that it's bad practice to transpile node_modules + deps, and that the consumer of client-side packages should assume / expect that they are already transpiled and es5 compatible (including their deps).

This was true for axios-extensions until version 3.1.3 and bumping lru-cache version broke this.

[krychu90]

+1
I had to downgrade to 3.1.2