loucadufault
loucadufault
> bindingless imports are assumed to be side-effecting, and thus can't ever be safely reordered (or anything moved across their boundary). That means you have to manually fix the ordering,...
Maybe I am missing something in your response, but I don't see how imports with bindings would mitigate such an issue. Trivial repro: ```js // side-effecting.js global.cannotExistYet = 'now it...
With that said, is the example above not proof that reordering imports having a binding after a side-effecting import (by convention) is problematic? I am not sure there is a...
I agree that it is unsafe to reorder "the module B import inside A" in your example above. Extending that, it must be unsafe to reorder the side-effecting import in...
edit: Opened a bug report: #2876
Also ran `tsc`, which is working with no errors.
@domoritz Anything specifically missing from the reproducible example provided in the ticket?
Considering it is a total of 4 LoC, how do you propose I minimize this further?
The issue is that the usage example from the README: https://github.com/dabroek/node-cache-manager-redis-store/blob/04d04cb5e5a472a9f8eb78c59fa1f90eb6df5839/README.md#single-store) no longer works with the latest version of "node-cache-manager": ```js // not awaiting here is the first issue, since...
I realize now that configuration files are only supported in JS, so this use case is not all that relevant (feel free to close)