Proposed GodotJS 1.1 / Godot 4.5 inclusions

.changeset/acher-neurogliosis-distance.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** Statically resolved return type for `get_node()`/`getNode()`.

.changeset/actinotoxemia-scryer-uncantoned.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** `ResourceLoader.load()` overload type.

.changeset/ammelide-dilute-nazarean.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** `@ExportObject(Node)` was only working for sub-classes, not `Node` itself.

.changeset/ammonifier-lungi-godmaker.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Duplicate "Generating" label appeared in the UI during codegen.

.changeset/appropinquate-hydrogeological-diipolia.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** `GDictionary` absent values are now correctly typed as returning as `null`, not `undefined`.

.changeset/arethuse-chlamydozoa-revere.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Improved type conversion error messages.

.changeset/asphyxiator-perceptionism-doorkeeper.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** `@export_` support for enums as keys of `GDictionary`.

.changeset/ballistae-pickaway-shelfpiece.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types/Fix:** Invalid codegen for certain types (function literals in particular)

.changeset/barter-uxorious-unsuspecting.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Background thread script instantiation (for 4.5 editor).

.changeset/beamlike-wartless-endamage.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Handle `hint_string` if `@export_var` is a `GArray` with an element type provided via `details.class_`.

.changeset/bedder-unvulgar-ungingled.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** Added `Resource` `duplicate()` return type.

.changeset/besiren-hodden-margarin.md

@@ -0,0 +1,25 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Improved user project type configurability.
+
+- Codegen for scenes and resources now default to being stored in
+  `gen/types` rather  than `typings/`. However, a setting has been
+  introduced to configure this. `typings/` is no longer used
+  because the directory is configured as a type root, which means
+  directories contained within are expected to be module
+  definitions.
+- `"types": ["node"]` in the default tsconfig was hiding type errors.
+  This is no longer set. Essentially, this setting was disabling
+  all types except node types from our type roots.
+- `@types/node` removed from the default `package.json`. It was
+  misleading and made it easy to accidentally use non-existent
+  functionality. We no longer need these types because...
+- Our JS essentials (console, timeout and intervals APIs) are now
+  included in our `godot.minimal.d.ts`.
+- No longer including `<reference no-default-lib=true/>` in our TS
+  files. This seemed to be interfering with user tsconfig options,
+  and it was not required. Not that it's been removed you're able to
+  more freely make changes to your tsconfig. For example, you may set
+  `libs` (or `target`) to make use of newer JS APIs.

.changeset/brighid-pit-mortcloth.md

@@ -0,0 +1,110 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Ergonomics overhaul. Camel-case, TS types, codegen + more.
+
+- There's now a project setting which can be toggled to swap to a
+  more idiomatic JS naming scheme for Godot bindings. We use
+  camel and pascal case to more closely align with typical
+  JavaScript/TypeScript conventions. For `@Decorators` we've gone
+  with pascal case, which is used in libraries like Angular. Camel
+  case is perhaps more popular, but pascal case allows us to avoid
+  reserved names, and thus we can cleanly write `@Export`, instead of
+  needing to include the trailing underscore on `@export_`.
+
+- TypeScript types have been improved. Particularly `Signal<>` and
+  `Callable<>`. `Signal1`, `Signal2`, etc. are now deprecated, as are
+  `AnySignal` and `AnyCallable`, since the new `Signal<T>` and `Callable<T>`
+  types handle an arbitrary number of parameters. Importantly,
+  `Callable.bind(...)` is now accurately typed, so you'll receive
+  type errors when connecting to signals.
+
+- `GArray` and `GDictionary` now have a static `.create<T>()` method
+  which allows you to create nested data structures from literals
+  and benefit from full type checking. When a `GArray` or `GDictionary`
+  is expected as a property, a `.proxy()` can be provided in its
+  place.
+
+- Partially worked around https://github.com/microsoft/TypeScript/issues/43826
+  whereby our proxied `GArray` and `GDictionary` always return proxied
+  nested values, but will accept non-proxied values when mutating
+  a property. Basically, there's now `GArrayReadProxy` and
+  `GDictionaryReadProxy`. These aren't runtime types, they're just
+  TS types that make it easier to work with proxies. Under normal
+  circumstances, you likely won't need to know these types exist.
+
+- Codegen leveled up. Any TS module can now export a function
+  named `codegen` with the type `CodeGenHandler`. This function
+  will be called during codegen to allow you to optionally
+  augment type generation involving user-defined types. Consider,
+  for example, the `SceneNodes` codegen which previously only knew
+  how to handle Godot/native types in the scene hierarchy. When
+  a user type was encountered, it'd write the native type, which
+  is still useful, but it'd be nice to be able to include user
+  types. The reason we don't by default is user types are not
+  required to follow our generic parameter convention where
+  each node is passed a `Map` argument.
+
+  Let's see an example:
+
+  ```ts
+    export default class CardCollection<Card extends CardNode = CardNode> extends GameNode<SceneNodes['scenes/card_collection_3d.tscn']>
+  ```
+
+  the type above does not take a `Map`. Perhaps more interesting, it
+  takes a different generic parameter, a `CardNode`. If we encounter
+  a `CardCollection` script attached to a node in the scene somewhere,
+  GodotJS' internal codegen can't possibly know what that generic
+  parameter ought to be. So we can help it out. In the same file
+  where `CardCollection` is defined, we could provide a `codegen`
+  handler like so:
+
+  ```ts
+  export const codegen: CodeGenHandler = rawRequest => {
+    const request = rawRequest.proxy();
+
+    switch (request.type) {
+      case CodeGenType.ScriptNodeTypeDescriptor: {
+        const cardNodeScript = request.node.get('cardNodeScript');
+        return GDictionary.create<UserTypeDescriptor>({
+          type: DescriptorType.User,
+          name: 'CardCollection',
+          resource: 'res://src/card-collection.ts',
+          arguments: GArray.create<TypeDescriptor>([
+            GDictionary.create<UserTypeDescriptor>({
+              type: DescriptorType.User,
+              name: cardNodeScript?.getGlobalName() ?? 'CardNode',
+              resource: cardNodeScript?.resourcePath ?? 'res://src/card-node.ts',
+            }),
+          ]),
+        });
+      }
+    }
+
+    return undefined;
+  };
+  ```
+
+  Above we handle the codegen request to determine the node type
+  of the provided `request.node`. What's *really* neat here is we
+  don't need to hard-code that generic. We've instead exported a
+  configurable `Script` reference for use in the editor:
+
+  ```ts
+    @ExportObject(Script)
+    cardNodeScript: Script = ResourceLoader.load('res://src/card-node.ts') as Script;
+  ```
+
+  So the codegen logic simply grabs the type exported from the
+  chosen script, and provides it as a generic argument to
+  `CardCollection<>`.
+
+  One thing worth noting, your class does NOT need to be a `@Tool`.
+  In the above example, `CardCollection<T>` is not a `@Tool`, and
+  hence the node script is not instantiated during codegen, which
+  is why we've used `request.node.get('cardNodeScript')` rather
+  than trying to access the property directly. That said, if you
+  want, codegen can be combined with `@Tool`.
+
+- There's also a bunch of logging/error reporting improvements.

.changeset/canadine-knowableness-leucitis.md

@@ -0,0 +1,16 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Godot String methods now exposed as static methods on `String`.
+
+This doesn't change anything about how strings are used within
+JavaScript i.e. we're still using JS native string type, not
+Godot's String. However, Godot's String class has many utility
+functions, some of them static and some of them as instance
+methods. These are now all available for consumption in JavaScript.
+Godot String instance methods are mapped to static methods that
+take a `target: string` as their first parameter.
+
+In general, if there's an equivalent native JS string method, you
+should always use it instead since it will be much more performant.

.changeset/cantabrize-infrigidation-spousy.md

@@ -0,0 +1,61 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Constructor params support and GDScript compatible `new`
+
+Support for `new` is very important for improving interop with
+other scripting languages, allowing them to instantiate objects
+from a Script reference. Crucially, this allows native
+GDExtension to instantiate Nodes/Objects/Resources implemented
+in GodotJS.
+
+Object construction has been refactored. Previously we had three
+cases to handle:
+
+1. new SomeJSWrapperAroundAGodotObject() – JS construction
+2. CDO (Class default object) construction - used to determine
+   default parameters on a class (for use in the editor).
+3. Cross binding. Which is when a Godot Object is constructed and
+   our script latter needs to attach to it.
+
+In the past, case 1 was the only situation in which instantiating
+a JS class ought to also instantiate the Godot native object.
+However, in my previous commit I changed CDOs so also instantiate
+the underlying native object. So case 2 was eliminated.
+
+Case 3 (cross binding) is a common situation, it was previously
+implemented in a somewhat intrusive fashion. All JS objects were
+being constructed and passed a parameter as their first argument.
+This indicated whether the object was cross binding (or a CDO).
+This prevented users from (easily) implementing constructors, the
+user had to know about the internal parameter and pass this
+up through to super(). For the most part I imagine users (myself
+included) simply avoided using constructors. However, this
+complicated some code that would otherwise be trivial in GDScript
+or C# because the latter has constructors and the former _init.
+
+Consequently, I've implemented a new strategy to determine whether
+a constructor is being called from C++ (cross binding) or from JS.
+The implementation is quite straight forward, but arriving at this
+solution was not necessarily obvious. V8 doesn't expose APIs to
+intercept construction, and we can't naively use shared flags
+to mark a native constructor in progress because the solution
+needs to support reentrancy since during construction an object
+may instantiate other objects. Additionally, we can't just use
+different constructors (V8 templates) because there's issues with
+both sub-classing and `instanceof` detection.
+
+The solution was to take advantage of JS' `Reflect.construct` API.
+This allows us to call a constructor but have `new.target` set to
+an arbitrary constructable. `new.target` survives whilst
+traversing up through super() constructors (similar to how we
+previously passed arguments up). This let's us mark a particular
+instantiation as coming from C++. `Reflect.construct` instantiates
+`this` to match the prototype chain from the provided `newTarget`
+so we simply set it to the prototype of the original constructor
+and we're on our way.
+
+Using `Reflect.construct` is also standard JS, so it's available
+on our support JS runtimes without needing to resort to any
+runtime-specific code.

.changeset/catharticalness-amphicarpous-unshewed.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** Improved GObject types

.changeset/chondrosteoma-keratoleukoma-tentaculocyst.md

@@ -0,0 +1,9 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Bind script instance during default prop evaluation.
+
+If properties are implemented in JavaScript as properties (getters)
+they'll often want to call Godot methods on self. Without the
+script instance being bound this led to a crash.

.changeset/clancularly-rattlejack-maguey.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Introduced a setting to control whether `.d.ts` for scenes are auto-generated on when scenes are saved in the Editor.

.changeset/convolvulinolic-mascouten-evanesce.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Expose Godot Variant utility method typeof() as `godot_typeof()`/`godotTypeof()`.

.changeset/crate-heteromera-runnel.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Threading / Godot address reuse crash.

.changeset/cresylite-unjudiciously-misshapen.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** Codegen + type checking for animations.

.changeset/cylindrella-prediluvial-araneology.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** `CameraFeed` types.

.changeset/cymraeg-recappable-porousness.md

@@ -0,0 +1,7 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types/Fix:** Codegen now types more `GArray`/`GDictionary` generic params based on exported variable hint strings.
+
+Additionally, fixed some codegen for enums when camel-case bindings are enabled.

.changeset/decretorily-enveil-misexplain.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Support async module loader in quickjs.impl.

.changeset/embryotome-papilioninae-troostitic.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature:** Godot 4.5 support

.changeset/epimachinae-anemonal-unbearableness.md

@@ -0,0 +1,11 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** "Generate Godot d.ts" in the UI is now "Generate types" and in addition to
+generating all Godot and project types (which it already did), the
+autogen directory will now be wiped of all files/directories before
+commencing generation. This ensures old generated files no longer
+pollute the project.
+
+

.changeset/epitrichium-dacite-fibrinolytic.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Duplicate PackedByteArray to_array_buffer() registration

.changeset/equity-clarionet-subtenancy.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Fix:** Added missing `PROPERTY_USAGE_SCRIPT_VARIABLE` flag on exported variables.

.changeset/ethnobiological-elfenfolk-semola.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** `NodePathMap` now permits `undefined`/optional children.

.changeset/exosmotic-pedatisect-kaffir.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Feature/Types:** Types + codegen for project input actions.

.changeset/extracapsular-unchangeable-coleochaetaceous.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types:** `EditorUndoRedoManager` API types

.changeset/fasciolar-cloisonless-hymeniophore.md

@@ -0,0 +1,5 @@
+---
+"@godot-js/editor": patch
+---
+
+**Types**: Ensure the GAny union type includes null