Fix `Bun.sleepSync` to actually use milliseconds (#2242)

* Fix Bun.sleep/sleepSync to actually use milliseconds

`Bun.sleepSync` was accidentally treating its argument as seconds rather than milliseconds as the docs stated.  This is a breaking change in that the function now behaves as documented.  Fixed relevant tests.

* sleepSync: add more argument checking, tests

1 files changed, 32 insertions, 0 deletions

diff --git a/test/bun.js/sleepSync.test.ts b/test/bun.js/sleepSync.test.ts
new file mode 100644
index 000000000..dd2e8818a
--- /dev/null
+++ b/test/bun.js/sleepSync.test.ts
@@ -0,0 +1,32 @@
+import { it, expect } from "bun:test";
+import { sleepSync } from "bun";
+
+it("sleepSync uses milliseconds", async () => {
+  const start = Date.now();
+  sleepSync(5);
+  const end = Date.now();
+  expect(end - start).toBeGreaterThanOrEqual(5);
+  expect(end - start).toBeLessThan(10);
+});
+
+it("sleepSync with no arguments throws", async () => {
+  expect(() => sleepSync()).toThrow();
+});
+
+it("sleepSync with non-numbers throws", async () => {
+  expect(() => sleepSync(true)).toThrow();
+  expect(() => sleepSync(false)).toThrow();
+  expect(() => sleepSync("hi")).toThrow();
+  expect(() => sleepSync({})).toThrow();
+  expect(() => sleepSync([])).toThrow();
+  expect(() => sleepSync(undefined)).toThrow();
+  expect(() => sleepSync(null)).toThrow();
+});
+
+it("sleepSync with negative number throws", async () => {
+  expect(() => sleepSync(-10)).toThrow();
+});
+
+it("can map with sleepSync", async () => {
+  [1, 2, 3].map(sleepSync);
+});