bun-types 1.1.42-canary.20241231T140524 → 1.1.42-canary.20250102T140513

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/docs/api/cc.md CHANGED
@@ -179,16 +179,16 @@ type Flags = string | string[];
179
179
 
180
180
  These are flags like `-I` for include directories and `-D` for preprocessor definitions.
181
181
 
182
- #### `defines: Record<string, string>`
182
+ #### `define: Record<string, string>`
183
183
 
184
- The `defines` is an optional object that should be passed to the TinyCC compiler.
184
+ The `define` is an optional object that should be passed to the TinyCC compiler.
185
185
 
186
186
  ```ts
187
187
  type Defines = Record<string, string>;
188
188
 
189
189
  cc({
190
190
  source: "hello.c",
191
- defines: {
191
+ define: {
192
192
  "NDEBUG": "1",
193
193
  },
194
194
  });
@@ -72,6 +72,8 @@ $ bun install --yarn
72
72
  print = "yarn"
73
73
  ```
74
74
 
75
+ {% /codetabs %}
76
+
75
77
  ### Text-based lockfile
76
78
 
77
79
  Bun v1.1.39 introduced `bun.lock`, a JSONC formatted lockfile. `bun.lock` is human-readable and git-diffable without configuration, at [no cost to performance](https://bun.sh/blog/bun-lock-text-lockfile#cached-bun-install-gets-30-faster).
@@ -90,8 +92,6 @@ Once `bun.lock` is generated, Bun will use it for all subsequent installs and up
90
92
 
91
93
  Bun v1.2.0 will switch the default lockfile format to `bun.lock`.
92
94
 
93
- {% /codetabs %}
94
-
95
95
  {% details summary="Configuring lockfile" %}
96
96
 
97
97
  ```toml
package/package.json CHANGED
@@ -1,5 +1,5 @@
1
1
  {
2
- "version": "1.1.42-canary.20241231T140524",
2
+ "version": "1.1.42-canary.20250102T140513",
3
3
  "name": "bun-types",
4
4
  "license": "MIT",
5
5
  "main": "",