Immer: Plugin not loaded for @xstate/immer

Created on 22 Oct 2020  ·  4Comments  ·  Source: immerjs/immer

🙋‍♂ Question

I am making it like a question because I don't have enough for reproduction. I am using @xstate/immer which is a fairly simple binding for XState. Today I started getting errors from the production like:

[Immer] minified error nr: 19 ES5. Find the full error at: https://bit.ly/3cXEKWf

Looking at the error list I see that "plugin not loaded", but I have no idea what that means. The binding doesn't seem to use any plugins.

Link to repro

Did not really manage to reproduce this locally and I have fairly extensive automated tests.

Environment

Even though @xstate/immer is configured with Immer V6, running yarn why immer in the project I am getting [email protected]. Could it be there isn't some breaking change handled properly?

_Sorry, if I am too vague. I am rather tired from launching product after 8-month work 💦_

question

Most helpful comment

Correct, just a KB extra, which mostly matters for hypothetical discussions
so loved by programmers :P

On Fri, Oct 23, 2020 at 10:53 AM Daniel K. notifications@github.com wrote:

Right, that makes sense, should have realized that seeing ES5 in the
message and it's coming from IE11. Are there any drawbacks to enabling it?
As I understand from docs, it's just a fallback and it won't affect other
users?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/691#issuecomment-715235447, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBFLZLKVKRI6YX53MNTSMFHCPANCNFSM4S3USGKA
.

All 4 comments

It means that enableES5() needs to be called if you want to support Immer in browsers that don't support Proxy

Right, that makes sense, should have realized that seeing ES5 in the message and it's coming from IE11. Are there any drawbacks to enabling it? As I understand from docs, it's just a fallback and it won't affect other users?

Correct, just a KB extra, which mostly matters for hypothetical discussions
so loved by programmers :P

On Fri, Oct 23, 2020 at 10:53 AM Daniel K. notifications@github.com wrote:

Right, that makes sense, should have realized that seeing ES5 in the
message and it's coming from IE11. Are there any drawbacks to enabling it?
As I understand from docs, it's just a fallback and it won't affect other
users?


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/691#issuecomment-715235447, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBFLZLKVKRI6YX53MNTSMFHCPANCNFSM4S3USGKA
.

Yeah, will unminify the exception in the next version, as this exception is
something that is more likely to escape the dev street

On Fri, Oct 23, 2020 at 11:21 AM Daniel K. notifications@github.com wrote:

Closed #691 https://github.com/immerjs/immer/issues/691.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/immerjs/immer/issues/691#event-3913232459, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN4NBATAMJH6D7GZS44LKTSMFKLTANCNFSM4S3USGKA
.

Was this page helpful?
0 / 5 - 0 ratings