You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've encountered the following error message when tried to use a browserified version of [email protected] in BigQuery:
TypeError: base intrinsic for Date.prototype.getTime exists, but the property is not available ...
The way I bundled the library
browserify -r @turf/turf -s turf > turf7.js
Then used it in a BQ UDF as follows:
CREATE TEMP FUNCTION tst()
RETURNS STRING
LANGUAGE js
OPTIONS (
library=["gs://.../turf7.js"]
) AS"""""";
SELECT tst()
As a workaround, I created the entry point JS file and added this line
Date.prototype.getTime=()=>{};
before requiring the library.
It looks like this issue is caused by the deep-equal library that references getTimehere.
Not sure if there are any action items for this issue -- after all, it probably should be filed against deep-equal, so feel free to close it. Just wanted to log it here for anyone encountering similar issues.
Cheers,
Sergey
The text was updated successfully, but these errors were encountered:
@svbatalov FYI both those PRs were released part of Turf 7.1.0. Will close this issue as resolved assuming it won't be an problem once you've upgraded. Reopen if you're still having an issue though.
Hello. Thanks for this great library!
I've encountered the following error message when tried to use a browserified version of [email protected] in BigQuery:
The way I bundled the library
browserify -r @turf/turf -s turf > turf7.js
Then used it in a BQ UDF as follows:
As a workaround, I created the entry point JS file and added this line
before requiring the library.
It looks like this issue is caused by the
deep-equal
library that referencesgetTime
here.Not sure if there are any action items for this issue -- after all, it probably should be filed against
deep-equal
, so feel free to close it. Just wanted to log it here for anyone encountering similar issues.Cheers,
Sergey
The text was updated successfully, but these errors were encountered: