bun-types 1.2.17-canary.20250617T140621 → 1.2.17-canary.20250619T140629

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CLAUDE.md CHANGED
@@ -17,6 +17,18 @@ Default to using Bun instead of Node.js.
17
17
  - Prefer `Bun.file` over `node:fs`'s readFile/writeFile
18
18
  - Bun.$`ls` instead of execa.
19
19
 
20
+ ## Testing
21
+
22
+ Use `bun test` to run tests.
23
+
24
+ ```ts#index.test.ts
25
+ import { test, expect } from "bun:test";
26
+
27
+ test("hello world", () => {
28
+ expect(1).toBe(1);
29
+ });
30
+ ```
31
+
20
32
  ## Frontend
21
33
 
22
34
  Use HTML imports with `Bun.serve()`. Don't use `vite`. HTML imports fully support React, CSS, Tailwind.
package/docs/api/fetch.md CHANGED
@@ -337,7 +337,7 @@ This will print the request and response headers to your terminal:
337
337
  ```sh
338
338
  [fetch] > HTTP/1.1 GET http://example.com/
339
339
  [fetch] > Connection: keep-alive
340
- [fetch] > User-Agent: Bun/1.2.17-canary.20250617T140621
340
+ [fetch] > User-Agent: Bun/1.2.17-canary.20250619T140629
341
341
  [fetch] > Accept: */*
342
342
  [fetch] > Host: example.com
343
343
  [fetch] > Accept-Encoding: gzip, deflate, br
package/docs/api/spawn.md CHANGED
@@ -120,7 +120,7 @@ You can read results from the subprocess via the `stdout` and `stderr` propertie
120
120
  ```ts
121
121
  const proc = Bun.spawn(["bun", "--version"]);
122
122
  const text = await new Response(proc.stdout).text();
123
- console.log(text); // => "1.2.17-canary.20250617T140621"
123
+ console.log(text); // => "1.2.17-canary.20250619T140629"
124
124
  ```
125
125
 
126
126
  Configure the output stream by passing one of the following values to `stdout/stderr`:
package/docs/api/utils.md CHANGED
@@ -582,11 +582,11 @@ Compresses a `Uint8Array` using zlib's DEFLATE algorithm.
582
582
  const buf = Buffer.from("hello".repeat(100));
583
583
  const compressed = Bun.deflateSync(buf);
584
584
 
585
- buf; // => Uint8Array(25)
586
- compressed; // => Uint8Array(10)
585
+ buf; // => Buffer(500)
586
+ compressed; // => Uint8Array(12)
587
587
  ```
588
588
 
589
- The second argument supports the same set of configuration options as [`Bun.gzipSync`](#bungzipsync).
589
+ The second argument supports the same set of configuration options as [`Bun.gzipSync`](#bun-gzipsync).
590
590
 
591
591
  ## `Bun.inflateSync()`
592
592
 
@@ -0,0 +1,65 @@
1
+ `bun info` displays package metadata from the npm registry.
2
+
3
+ ## Usage
4
+
5
+ ```bash
6
+ $ bun info react
7
+ ```
8
+
9
+ This will display information about the `react` package, including its latest version, description, homepage, dependencies, and more.
10
+
11
+ ## Viewing specific versions
12
+
13
+ To view information about a specific version:
14
+
15
+ ```bash
16
+ $ bun info react@18.0.0
17
+ ```
18
+
19
+ ## Viewing specific properties
20
+
21
+ You can also query specific properties from the package metadata:
22
+
23
+ ```bash
24
+ $ bun info react version
25
+ $ bun info react dependencies
26
+ $ bun info react repository.url
27
+ ```
28
+
29
+ ## JSON output
30
+
31
+ To get the output in JSON format, use the `--json` flag:
32
+
33
+ ```bash
34
+ $ bun info react --json
35
+ ```
36
+
37
+ ## Alias
38
+
39
+ `bun pm view` is an alias for `bun info`:
40
+
41
+ ```bash
42
+ $ bun pm view react # equivalent to: bun info react
43
+ ```
44
+
45
+ ## Examples
46
+
47
+ ```bash
48
+ # View basic package information
49
+ $ bun info is-number
50
+
51
+ # View a specific version
52
+ $ bun info is-number@7.0.0
53
+
54
+ # View all available versions
55
+ $ bun info is-number versions
56
+
57
+ # View package dependencies
58
+ $ bun info express dependencies
59
+
60
+ # View package homepage
61
+ $ bun info lodash homepage
62
+
63
+ # Get JSON output
64
+ $ bun info react --json
65
+ ```
@@ -7,7 +7,7 @@ Use `bun publish` to publish a package to the npm registry.
7
7
  $ bun publish
8
8
 
9
9
  ## Output
10
- bun publish v1.2.17-canary.20250617T140621 (ca7428e9)
10
+ bun publish v1.2.17-canary.20250619T140629 (ca7428e9)
11
11
 
12
12
  packed 203B package.json
13
13
  packed 224B README.md
@@ -9,7 +9,7 @@ $ bunx nuxi init my-nuxt-app
9
9
  ✔ Which package manager would you like to use?
10
10
  bun
11
11
  ◐ Installing dependencies...
12
- bun install v1.2.17-canary.20250617T140621 (16b4bf34)
12
+ bun install v1.2.17-canary.20250619T140629 (16b4bf34)
13
13
  + @nuxt/devtools@0.8.2
14
14
  + nuxt@3.7.0
15
15
  785 packages installed [2.67s]
@@ -15,7 +15,7 @@ This will add the package to `peerDependencies` in `package.json`.
15
15
  ```json-diff
16
16
  {
17
17
  "peerDependencies": {
18
- + "@types/bun": "^1.2.17-canary.20250617T140621"
18
+ + "@types/bun": "^1.2.17-canary.20250619T140629"
19
19
  }
20
20
  }
21
21
  ```
@@ -27,7 +27,7 @@ Running `bun install` will install peer dependencies by default, unless marked o
27
27
  ```json-diff
28
28
  {
29
29
  "peerDependencies": {
30
- "@types/bun": "^1.2.17-canary.20250617T140621"
30
+ "@types/bun": "^1.2.17-canary.20250619T140629"
31
31
  },
32
32
  "peerDependenciesMeta": {
33
33
  + "@types/bun": {
@@ -97,7 +97,7 @@ $ bun update
97
97
  $ bun update @types/bun --latest
98
98
 
99
99
  # Update a dependency to a specific version
100
- $ bun update @types/bun@1.2.17-canary.20250617T140621
100
+ $ bun update @types/bun@1.2.17-canary.20250619T140629
101
101
 
102
102
  # Update all dependencies to the latest versions
103
103
  $ bun update --latest
@@ -21,7 +21,7 @@ Here's what the output of a typical test run looks like. In this case, there are
21
21
 
22
22
  ```sh
23
23
  $ bun test
24
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
24
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
25
25
 
26
26
  test.test.js:
27
27
  ✓ add [0.87ms]
@@ -47,7 +47,7 @@ To only run certain test files, pass a positional argument to `bun test`. The ru
47
47
 
48
48
  ```sh
49
49
  $ bun test test3
50
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
50
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
51
51
 
52
52
  test3.test.js:
53
53
  ✓ add [1.40ms]
@@ -85,7 +85,7 @@ Adding `-t add` will only run tests with "add" in the name. This works with test
85
85
 
86
86
  ```sh
87
87
  $ bun test -t add
88
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
88
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
89
89
 
90
90
  test.test.js:
91
91
  ✓ add [1.79ms]
@@ -18,7 +18,7 @@ The first time this test is executed, Bun will evaluate the value passed into `e
18
18
 
19
19
  ```sh
20
20
  $ bun test test/snap
21
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
21
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
22
22
 
23
23
  test/snap.test.ts:
24
24
  ✓ snapshot [1.48ms]
@@ -61,7 +61,7 @@ Later, when this test file is executed again, Bun will read the snapshot file an
61
61
 
62
62
  ```sh
63
63
  $ bun test
64
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
64
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
65
65
 
66
66
  test/snap.test.ts:
67
67
  ✓ snapshot [1.05ms]
@@ -78,7 +78,7 @@ To update snapshots, use the `--update-snapshots` flag.
78
78
 
79
79
  ```sh
80
80
  $ bun test --update-snapshots
81
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
81
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
82
82
 
83
83
  test/snap.test.ts:
84
84
  ✓ snapshot [0.86ms]
@@ -29,7 +29,7 @@ To regenerate snapshots, use the `--update-snapshots` flag.
29
29
 
30
30
  ```sh
31
31
  $ bun test --update-snapshots
32
- bun test v1.2.17-canary.20250617T140621 (9c68abdb)
32
+ bun test v1.2.17-canary.20250619T140629 (9c68abdb)
33
33
 
34
34
  test/snap.test.ts:
35
35
  ✓ snapshot [0.86ms]
@@ -5,7 +5,7 @@ name: Get the current Bun version
5
5
  Get the current version of Bun in a semver format.
6
6
 
7
7
  ```ts#index.ts
8
- Bun.version; // => "1.2.17-canary.20250617T140621"
8
+ Bun.version; // => "1.2.17-canary.20250619T140629"
9
9
  ```
10
10
 
11
11
  ---
@@ -14,7 +14,7 @@ Kernel version 5.6 or higher is strongly recommended, but the minimum is 5.1. Us
14
14
  ```bash#macOS/Linux_(curl)
15
15
  $ curl -fsSL https://bun.sh/install | bash # for macOS, Linux, and WSL
16
16
  # to install a specific version
17
- $ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.17-canary.20250617T140621"
17
+ $ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.17-canary.20250619T140629"
18
18
  ```
19
19
 
20
20
  ```bash#npm
@@ -189,10 +189,10 @@ Since Bun is a single binary, you can install older versions of Bun by re-runnin
189
189
 
190
190
  ### Installing a specific version of Bun on Linux/Mac
191
191
 
192
- To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.17-canary.20250617T140621`.
192
+ To install a specific version of Bun, you can pass the git tag of the version you want to install to the install script, such as `bun-v1.2.0` or `bun-v1.2.17-canary.20250619T140629`.
193
193
 
194
194
  ```sh
195
- $ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.17-canary.20250617T140621"
195
+ $ curl -fsSL https://bun.sh/install | bash -s "bun-v1.2.17-canary.20250619T140629"
196
196
  ```
197
197
 
198
198
  ### Installing a specific version of Bun on Windows
@@ -201,7 +201,7 @@ On Windows, you can install a specific version of Bun by passing the version num
201
201
 
202
202
  ```sh
203
203
  # PowerShell:
204
- $ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.17-canary.20250617T140621"
204
+ $ iex "& {$(irm https://bun.sh/install.ps1)} -Version 1.2.17-canary.20250619T140629"
205
205
  ```
206
206
 
207
207
  ## Downloading Bun binaries directly
@@ -124,11 +124,11 @@ await fetch("https://example.com", {
124
124
  This prints the `fetch` request as a single-line `curl` command to let you copy-paste into your terminal to replicate the request.
125
125
 
126
126
  ```sh
127
- [fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.17-canary.20250617T140621" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
127
+ [fetch] $ curl --http1.1 "https://example.com/" -X POST -H "content-type: application/json" -H "Connection: keep-alive" -H "User-Agent: Bun/1.2.17-canary.20250619T140629" -H "Accept: */*" -H "Host: example.com" -H "Accept-Encoding: gzip, deflate, br" --compressed -H "Content-Length: 13" --data-raw "{\"foo\":\"bar\"}"
128
128
  [fetch] > HTTP/1.1 POST https://example.com/
129
129
  [fetch] > content-type: application/json
130
130
  [fetch] > Connection: keep-alive
131
- [fetch] > User-Agent: Bun/1.2.17-canary.20250617T140621
131
+ [fetch] > User-Agent: Bun/1.2.17-canary.20250619T140629
132
132
  [fetch] > Accept: */*
133
133
  [fetch] > Host: example.com
134
134
  [fetch] > Accept-Encoding: gzip, deflate, br
@@ -170,7 +170,7 @@ This prints the following to the console:
170
170
  [fetch] > HTTP/1.1 POST https://example.com/
171
171
  [fetch] > content-type: application/json
172
172
  [fetch] > Connection: keep-alive
173
- [fetch] > User-Agent: Bun/1.2.17-canary.20250617T140621
173
+ [fetch] > User-Agent: Bun/1.2.17-canary.20250619T140629
174
174
  [fetch] > Accept: */*
175
175
  [fetch] > Host: example.com
176
176
  [fetch] > Accept-Encoding: gzip, deflate, br
package/docs/test/dom.md CHANGED
@@ -55,7 +55,7 @@ Let's run this test with `bun test`:
55
55
 
56
56
  ```bash
57
57
  $ bun test
58
- bun test v1.2.17-canary.20250617T140621
58
+ bun test v1.2.17-canary.20250619T140629
59
59
 
60
60
  dom.test.ts:
61
61
  ✓ dom test [0.82ms]
package/package.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.2.17-canary.20250617T140621",
2
+ "version": "1.2.17-canary.20250619T140629",
3
3
  "name": "bun-types",
4
4
  "license": "MIT",
5
5
  "types": "./index.d.ts",