@girs/glib-2.0 2.78.0-3.2.4 → 2.78.0-3.2.6
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/README.md +14 -1
- package/glib-2.0-ambient.d.ts +0 -1
- package/glib-2.0-import.d.ts +0 -1
- package/glib-2.0.d.cts +5 -0
- package/glib-2.0.d.ts +5 -0
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -5,7 +5,7 @@
|
|
|
5
5
|

|
|
6
6
|
|
|
7
7
|
|
|
8
|
-
GJS TypeScript type definitions for GLib-2.0, generated from library version 2.78.0 using [ts-for-gir](https://github.com/gjsify/ts-for-gir) v3.2.
|
|
8
|
+
GJS TypeScript type definitions for GLib-2.0, generated from library version 2.78.0 using [ts-for-gir](https://github.com/gjsify/ts-for-gir) v3.2.6.
|
|
9
9
|
|
|
10
10
|
GLib provides the core application building blocks for libraries and applications written in C. It provides the core object system used in GNOME, the main loop implementation, and a large set of utility functions for strings and common data structures.
|
|
11
11
|
|
|
@@ -82,6 +82,19 @@ Now you have also type support for this, too:
|
|
|
82
82
|
const GLib = imports.gi.GLib;
|
|
83
83
|
```
|
|
84
84
|
|
|
85
|
+
|
|
86
|
+
### ESM vs. CommonJS
|
|
87
|
+
|
|
88
|
+
GJS supports two different import syntaxes. The new modern ESM syntax and the old global imports syntax.
|
|
89
|
+
|
|
90
|
+
In TypeScript projects for GJS and GNOME Shell extensions, you have the flexibility to use `ESM` syntax and then decide the import syntax for your bundled file. If your bundler is configured to use `CommonJS`, it will convert to the GJS-specific global imports syntax, like `const moduleName = imports.gi[moduleName]`. This is different from the traditional `require` syntax seen in Node.js. The global imports syntax is chosen because it aligns with the CommonJS format supported by NPM, which is used for the generated type definitions and this package.
|
|
91
|
+
|
|
92
|
+
On the other hand, if you configure your bundler to use ESM, it will retain the ESM import syntax. It's crucial to ensure that your bundler is set up to correctly translate and bundle these imports into either CommonJS or ESM format, depending on your project's requirements.
|
|
93
|
+
|
|
94
|
+
This approach is particularly important due to the `@girs` types, which include both `*.cjs `files, using the GJS global imports syntax, and `*.js` files, which utilize the ESM syntax. By appropriately setting up your bundler, you can control which syntax—CommonJS or ESM—is used in your project. The choice of CommonJS in this context is also due to the similarity between the GJS-specific global imports and CommonJS syntax, allowing for easier management and bundling in these specific types of projects.
|
|
95
|
+
|
|
96
|
+
Since GNOME Shell 45, you should only use ESM, even for GNOME Shell extensions. Before that, extensions had to use the global import syntax, unlike normal GJS applications, where ESM has been available for some time.
|
|
97
|
+
|
|
85
98
|
### Bundle
|
|
86
99
|
|
|
87
100
|
Depending on your project configuration, it is recommended to use a bundler like [esbuild](https://esbuild.github.io/). You can find examples using different bundlers [here](https://github.com/gjsify/ts-for-gir/tree/main/examples).
|
package/glib-2.0-ambient.d.ts
CHANGED
package/glib-2.0-import.d.ts
CHANGED
package/glib-2.0.d.cts
CHANGED
|
@@ -17895,6 +17895,11 @@ export interface MainLoop {
|
|
|
17895
17895
|
* the result is zero, free the loop and free all associated memory.
|
|
17896
17896
|
*/
|
|
17897
17897
|
unref(): void
|
|
17898
|
+
/**
|
|
17899
|
+
* Similar to `GLib.MainLoop.run` but return a Promise which resolves when the main loop ends, instead of blocking while the main loop runs.
|
|
17900
|
+
* This helps avoid the situation where Promises never resolved if you didn't run the main loop inside a callback.
|
|
17901
|
+
*/
|
|
17902
|
+
runAsync(): Promise<void>
|
|
17898
17903
|
}
|
|
17899
17904
|
|
|
17900
17905
|
/**
|
package/glib-2.0.d.ts
CHANGED
|
@@ -17897,6 +17897,11 @@ interface MainLoop {
|
|
|
17897
17897
|
* the result is zero, free the loop and free all associated memory.
|
|
17898
17898
|
*/
|
|
17899
17899
|
unref(): void
|
|
17900
|
+
/**
|
|
17901
|
+
* Similar to `GLib.MainLoop.run` but return a Promise which resolves when the main loop ends, instead of blocking while the main loop runs.
|
|
17902
|
+
* This helps avoid the situation where Promises never resolved if you didn't run the main loop inside a callback.
|
|
17903
|
+
*/
|
|
17904
|
+
runAsync(): Promise<void>
|
|
17900
17905
|
}
|
|
17901
17906
|
|
|
17902
17907
|
/**
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@girs/glib-2.0",
|
|
3
|
-
"version": "2.78.0-3.2.
|
|
3
|
+
"version": "2.78.0-3.2.6",
|
|
4
4
|
"description": "GJS TypeScript type definitions for GLib-2.0, generated from library version 2.78.0",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"module": "glib-2.0.js",
|
|
@@ -25,8 +25,8 @@
|
|
|
25
25
|
"test:cjs": "NODE_OPTIONS=--max_old_space_size=9216 tsc --noEmit glib-2.0.d.cts"
|
|
26
26
|
},
|
|
27
27
|
"dependencies": {
|
|
28
|
-
"@girs/gjs": "^3.2.
|
|
29
|
-
"@girs/gobject-2.0": "^2.78.0-3.2.
|
|
28
|
+
"@girs/gjs": "^3.2.6",
|
|
29
|
+
"@girs/gobject-2.0": "^2.78.0-3.2.6"
|
|
30
30
|
},
|
|
31
31
|
"devDependencies": {
|
|
32
32
|
"typescript": "*"
|