Cannot read property 'Symbol(toStringTag)' of undefined for

[Jaans]

The new Aurelia polyfills is erroring out when a null or undefined value is passed for the Object.prototype.toString polyfill.

I found the source usage that is receiving the above Aurelia error inside the momentjs library where it checks input using the Object.prototype (see screenshot below):

Let me know if you need more info.

[EisenbergEffect]

We have a fix coming.

[NateRedding]

I got this error as well. I think the core.js library has the same issue also. When I tried importing core-js from main.js, I get the same error message, but a different stacktrace (obviously).

[mthomson]

I rolled back to core-js and this error has gone away. I'm putting the core-js client right into index.html

[EisenbergEffect]

Putting core-js in the index.html is probably the easiest way to ensure that it works correctly. We do have a fix for this particular issue coming shortly.

[damianof]

How can we update our packages references without getting this latest bug? It seems this start from aurelia-bootstrapper which is the one who has a reference to the aurelia-polyfills

[EisenbergEffect]

Fixed. Release coming shortly.

[damianof]

Thank you Rob.

[damianof]

Ok now there is no more errors, but the application no longer renders.

[betrayedjinn]

For me, its working fine now.

[damianof]

paranoxx, did you try cleaning everything, node modules, jspm packages, dist, and start from scratch with npm install, then jspm update then gulp build?

[betrayedjinn]

No, why should i?

[Jaans]

Excellent! Issue fixed. Thank you for the quick turnaround.

[damianof]

paranoxx, you should not, but if you do you'll experience my issue. This might be unrelated to this issue, and I'm currently still trying to figure out which other updates to which other aurelia package is causing this. I only know that my app was working fine until the last 2-3 days.

[betrayedjinn]

Shoudn't you do a jspm install -y after a clean?

[damianof]

paranoxx You should not have too. I usually never do jspm install -y. Let me dig a little more into my config and see what I can find. I' put together a little solution with a subset and I'll post on github public shortly

[betrayedjinn]

I'm not that into the internals of jspm but that's what i do while preparing deployment. Checkout project on destination server, npm install followed by jspm install -y followed by gulp bundle.

[damianof]

paranoxx all seems working again in my sandbox here https://github.com/damianof/aurelia-config-samples

[leosbrf]

Should that fix also cover null values? I'm getting a similar error when null.

Edited: done in commit: https://github.com/aurelia/polyfills/commit/4b705bb1c4886e197d0e8dfcc291fb3308238372