Edge: SCRIPT1028: Expected identifier, string or number
As of 2020-05-12 this will work in Microsoft Edge. Tested version: Microsoft Edge Version 81.0.416.72 (Official build) (64-bit)
https://www.microsoft.com/en-us/edge
The following lines of code caused the exception SCRIPT1028: Expected identifier, string or number
but when updating everything worked:
return {
...state,
products: [...state.products, ...action.payload],
};
Neither Edge nor IE support object property rest syntax (though Edge will likely support it eventually). I'd suggest automatically transpiling your code to ES5 with Babel, which will allow you to write in the latest and greatest version of the language, while allowing ancient and incompatible browsers to understand all of your transpiled code. For example, plugging in
const { category, ...rest } = c;
results in
"use strict";
function _objectWithoutProperties(obj, keys) { var target = {}; for (var i in obj) { if (keys.indexOf(i) >= 0) continue; if (!Object.prototype.hasOwnProperty.call(obj, i)) continue; target[i] = obj[i]; } return target; }
var _c = c,
category = _c.category,
rest = _objectWithoutProperties(_c, ["category"]);
Doesn't look so pretty, but it can be done automatically.
One manual way of doing it could be:
const c = {
category: 'category',
foo: 'foo',
bar: 'bar'
};
const category = c.category;
// Object.assign so as not to mutate the original object:
const rest = Object.assign({}, c);
delete rest.category;
console.log(rest);
It appears (surprisingly) that Edge doesn't support property rest yet, which is unfortunate but then it was officially added only in ES2018. You'll need to rewrite the code not to use property rest (the ...rest
part of your object literal) (or, as CertainPerformance suggests, use a transpiler).
Here's one of many ways to do that:
function sortByCategory(data) {
return data.reduce((obj, c) => {
//const { category, ...rest } = c;
const { category } = c;
const rest = {};
for (const key of Object.keys(c)) {
if (key !== "category") {
rest[key] = c[key];
}
}
obj[category] = obj[category] || [];
obj[category].push(rest);
return obj;
}, {});
}
I avoided using delete
because delete
on an object de-optimizes the object, making property lookups slower. But deoptimizing just these objects may well not make any difference to the perceived speed of your page/app, so...
In case you have node package ecosystem:
- Update browser list in your package.json
{
...
"browserslist": {
"production": [
...
],
"development": [
"last 1 chrome version",
"last 1 firefox version",
"last 1 safari version",
"last 1 ie version" // <- make sure this is present
]
},
...
}
- Delete .cache folder in node_modules
- Re-run the dev server