I’m glad you narrowed down the issue but I’m not really aware of this specific library. I personally managed to push our only client using IE to stop using it but I know this is not an option for everyone.
I went through a big refactor - updating packages and shifting to react hooks, and came up with this dreaded error!
You really need to narrow down on the culprit package
Any tips on how to go about narrowing down the culprit? IE devtools are zero help (I’ve spent a day setting up a virtual Windows 10 machine to get the IE environment going, along with installing and setting up Meteor on the VM).
Jump to that line in modules and check what’s going on there.
Had a similar issue last week which was solvable by downgrading simple schema as the lib uses class syntax in the latest version which is not supported by ie11.
Specifically v1.5.5 is the last correctly compiled version of simpl-schema.
You can pin it with npm install firstname.lastname@example.org. Be sure to commit your package-lock.json as well to ensure it uses the right version.
I’ve got a PR in to fix the incorrect compilation for browsers.