15 Commits
Author SHA1 Message Date
Robert KiefferandGitHub 6a1b881b49 fix!: expect crypto to be global everywhere (requires node@20+) (#935) 2026-04-19 03:01:26 -10:00
Robert KiefferandGitHub 7d21f67708 chore: switch to Biome for parsing and linting (#932) 2026-04-05 04:45:29 -10:00
Robert KiefferandGitHub 84a8145fa7 chore: fix remaining issues for v11 release (#789) 2024-09-05 10:41:51 -10:00
Robert KiefferandGitHub c244b0da28 feat!: Port to TypeScript, closes #762 (#763)
Ports all code to Typescript.  TS users should no longer need to install `@types/uuid`.
2024-07-16 07:55:56 -10:00
Robert KiefferandGitHub 7305b4aa4a chore: update package dependencies (#752) 2024-06-05 02:16:12 -10:00
Christoph TavanandGitHub a21b1103ff build: drop support for legacy browsers (IE11, Safari 10) (#604)
BREAKING CHANGE: Drop support for browsers that don't correctly
implement const/let and default arguments, and no longer transpile the
browser build to ES2015.

This also removes the fallback on msCrypto instead of the crypto API.

Browser tests are run in the first supported version of each supported
browser and in the latest (as of this commit) version available on
Browserstack.
2022-08-04 00:12:10 +02:00
Christoph TavanandGitHub 8500ad7b7d chore: use Node.js 16.x for building package and tests (#601)
Also upgrade `@wdio@6` -> `@wdio@7` since `@wdio@6` doesn't work with Node.js 16.
2021-12-02 23:14:02 +01:00
Linus UnnebäckandGitHub c8b6ff6460 feat: use native crypto.randomUUID when available (#600) 2021-12-02 10:04:00 +01:00
Christoph TavanandGitHub 39574582ec test: optimize browser test order (#492)
Wdio executes tests in order. We have 5 concurrent execution slots at
BrowserStack. Since the IE tests take by far the longest time (1:30
instead of 0:30 for all others) it makes sense to run them first. Safari
tests seem to execute the fastes, so run them last.
2020-07-23 10:39:59 +02:00
Christoph TavanandGitHub a9ad5cfe2a test: increase wdio timout (#491)
With the added tests IE11 tests have become flaky since they simply seem
too sloooooooooooow. The tests in IE11 take up to 1:30 to run while they
usually finish after around 30s in all other browsers.
2020-07-23 00:09:32 +02:00
391190bee3 feat: add parse/stringify/validate/version/NIL APIs (#479)
Add the following new APIs:
- uuid.NIL The nil UUID string (all zeros)
- uuid.parse() Convert UUID string to array of bytes
- uuid.stringify() Convert array of bytes to UUID string
- uuid.validate() Test a string to see if it is a valid UUID
- uuid.version() Detect RFC version of a UUID

This commit also adds more accurate validation when stringifying UUIDs and improves UUID parsing performance (for v3/v5 UUIDs) significantly (Thanks @awwit!).

Co-authored-by: Christoph Tavan <[email protected]>
Co-authored-by: Ignat Prokopovich <[email protected]>
Co-authored-by: Robert Kieffer <[email protected]>
Co-authored-by: Linus Unnebäck <[email protected]>
2020-07-22 22:32:20 +02:00
Christoph TavanandGitHub b4fa34970f test: remove flaky Edge 18.0 on Windows 10 test (#471)
Browserstack seems to have trouble accessing the local proxy on recent
Edge 18.0 / Windows 10 machines. Since Edge 18.0 is deprecated anyways
and since we still have an Edge 15.0 test as a safety net it should be
fine to just drop the Edge 18.0 test.
2020-06-23 09:08:06 +02:00
Christoph TavanandGitHub 4764d19a3d test: support node 14 and latest browsers (#422)
* test: run CI on Node.js 14.x
* test: test on latest versions of chrome, edge and firefox
2020-04-24 11:36:41 +02:00
Christoph TavanandGitHub 23bc1f25e2 chore: upgrade all devDependencies (#412) 2020-04-14 10:19:23 +02:00
Christoph TavanandGitHub bdd25d0123 test: use webdriverio (#399)
Our current browser tests were incredibly flaky.

Webdriver.io seems to contain retry logic and other safeguards that we
are currently lacking in our custom browserstack-local /
selenium-webdriver setup.

Under the hood things should still work similarly, let's see if they are
now more stable.

Using the new setup I was able to observer 10 successful BrowserStack CI runs
in a row – which has never happened with the previous setup.
2020-03-05 16:11:33 +01:00