chore: allow running tests in IE11 on BrowserStack

[ovidiu1]

I have create a new npm script to run all tests in ie11 browser - browserstack

[bashmish]

I don't mind merging this as as since it has some value: you are allowed to run tests in IE11 on browserstack, but it does not close the issue #108, the problem is broader there, including the fact that we need to fix flaky tests as well. Also fix(scope) format assumes you put either a subpackage name as a scope, of if it impacts the entire monorepository, then you just leave it empty. Third, this is a chore type of commit because it does not impact the released code. So taking into account all of this please change the commit message to chore: allow running tests in IE11 on BrowserStack and I'll approve.

[bashmish]

I've realised that I was wrong. :legacy is for testing transpiled code everywhere, rather than for testing old browsers. So in fact the final logic will be like this:

1. modern config runs in browsers that support ES modules (modern Chrome, Firefox, Safari, Edge)
2. legacy config runs in all browsers (the ones above + IE11)

The reason it needs to be like this is because often the code is transpiled and run in production on every browser, while some people might have differential builds and serve different code based on browser agent sniffing. So basically transpiled code needs to work everywhere.

So I'm closing this MR. if you want to run tests for yourself, please use this terminal command:

yarn test:bs --legacy --browsers=bs_win10_ie_11

or more precisely - with BROWSER_STACK_USERNAME and BROWSER_STACK_ACCESS_KEY

BROWSER_STACK_USERNAME=%name% BROWSER_STACK_ACCESS_KEY=%key% yarn test:bs --legacy --browsers=bs_win10_ie_11