First thing’s first - Storybook is an awesome tool that allows you to develop/showcase your components. It has support for a whole range of frameworks and libraries and a bunch of useful addons. You should definitely check it out for your next project, or even your current one!
I maintain a component library and use Storybook as my developing environment. In addition, we use that same Storybook to showcase our components for consumers, that way they know what they can/can’t use.
Because we have Storybook, when getting a bug report, we can say things like “You need to supply steps to reproduce this in storybook”. That makes things much easier to maintain, I don’t have to dig up through another persons’ codebase just to reproduce a bug, I have an environment they can reproduce it in - Storybook.
For that reason, we look at our storybook as a “clean” environment, it renders one component each time. That way if something isn’t working with a component in a specific application - it probably is a case of bad usage because our components work in isolation.
After a recent change to one component we got complaints that this component behaved unexpectedly in IE11. Me, the good developer that I am, went to storybook to check if for some reason this got missed and indeed the component behaved differently in IE11.
I was happy to see that it did, so then I replied to that bug with a response of “Sorry, I can’t reproduce this on my side.”
Things calmed down for about a day and then it came back, this time with a bit more info - it tried to invoke a function called
e on an object, but
e was undefined on the object.
That was both an “aha!” and 😳 moment. “aha!” because I knew exactly where to look. 😳 because it didn’t make sense.
Before we dive deeper we need to talk about the actual code that’s changed, we need to talk about the new requirement. This requirement was for a component to sanitize urls that aren’t whitelisted - for that we added a new
whitelist parameter. This
whitelist is an array that could contain a string, regex or function.
constructor function and that every function has a
name so instead of doing an ugly condition I opted to create a
matchers object with 3 functions,
function and then do
matacher is the current matcher from the
So, by now you probably know that trying to call
e on that matchers object resulted in an exception because that object only had 3 functions and
e wasn’t one of them.
That’s where the “aha!” became 😳 - how is it possible? how could this be happening?
My first reaction was that I can’t reproduce this in Storybook which means that the consuming application is probably loading a faulty babel plugin or importing a bad polyfill that overrides the
RegExp constructor name (the only whitelist element was a
And so, I again responded with “In Storybook the consructor name for
RegExp works fine, this is something that needs to be fixed in the application not the component library.”
Another day passed and another clue came along with it - that same component didn’t work in IE11 for another application, not just that one specific application. This was odd, I can’t right this off to just coincidence, I need to go deeper.
I started looking around the web to see - was this something that just our apps didn’t have for some reason(a shared tooling problem maybe)? nope. Couldn’t find one site that has
obj.constructor.name in IE11 - what gives?
This had to be a polyfill issue, but how?
better check MDN for support for
constructor.name which seemed fine but then scrolling down was the browser compatibility table down at the bottom:
This is a step closer, we now know that IE doesn’t support names on functions (seriously?!), but it stil doesn’t explain everything. How does this work in Storybook? it was time to take off the gloves, it’s time to question everything - this bug could be anywhere, even Storybook.
It was time to take a look at our storybook. First thing was to remove all of the polyfills we loaded for the components, maybe one of them polyfilled another thing along the way? After removing all the polyfills and restarting storybook I was still amazed to see that
/hello/.constructor.name === 'RegExp' evaluated to true.
That’s really weird, but it’s someplace else - next up came Storybook itself, maybe it loaded the polyfill for some reason? How would be even start looking the Storybook code? How about searching for
polyfill? That’ll probably be a good start.
This is what I got:
There are a lot of angular specific stuff while I build my components in React.
Some of you already noticed the non-angular one but I missed it at first, I went down the wrong path and started looking at the client side code of the react app. Followed the main entry point of the react app, couldn’t find anything, looked for
core-js in package.json and it was there! that’s something right? couldn’t find where it was imported from inside the storybook react app.
We’re still not there though, let’s take a peek at
In order to do it accurately we need something else first, the specific
airbnb-shims version installed by storybook. If we look at the latest version it might not contain the culprit polyfill anymore.
Looking at the
lib/core gives us
"airbnb-shims": "^1 || ^2", so either version 1 or 2.
It’s time to look at
firstname.lastname@example.org and from the looks of it the latest version (at the time) was 2.1.1 so we could just look at that.
Digging through the code we see that all shims are loaded incrementally
Just to be 1000% sure that this is the real issue we do the same thing and find out the version of
function.prototype.name used by
airbnb-shims which is
^1.1.0 which is also currently the latest version, and again, we can take look at the current version. We open the
shim.js and revel in our victory:
Putting a breakpoint right before the
defineProperty call and waiting for the app to pause.
We then test
/hello/.constructor.name to find it’s
undefined, that’s a good start. Now for the punch, step over the
defineProperty call, test out
/hello/.constructor.name to see that it’s
RegExp! we have our answer! 🎉
All that was left to do now is submit an issue in Storybook.
Now that we’re done, we can look back and try to learn something from all of this. In the next few posts we’ll talk more about debugging and learn some techniques that will help us debug better and eventually solve more mysteries! 🔍