From 99e8ad00012db78e310c086f0cea8d1215844f6a Mon Sep 17 00:00:00 2001
From: Paladox none <thomasmulhall410@yahoo.com>
Date: Tue, 27 Feb 2024 20:24:22 +0000
Subject: Update git submodules

* Update plugins/delete-project from branch 'stable-3.7'
  to 8f6ea7eeb22f8b8487d3b433d367272172ea32d1
  - Add support for newer plugin-node-resolve versions

    Due to [0] in plugin-node-resolve, it changes the way modules are
    resolved. It now looks at package.json and figures it out from
    there although if the stuff it is looking for is not found
    it falls back to how it did the resolving in older versions.
    Unfortunately there is no config to force the behaviour
    so we have to use the new behaviour.

    This is what it looks like:

    ```
      "exports": {
        ".": {
          "development": "./development/reactive-element.js",
          "default": "./reactive-element.js"
        },
        ....
        "./decorators.js": {
          "development": "./development/decorators.js",
          "default": "./decorators.js"
        },
        ....
      },
    ```

    Thus "./decorators" fails to match "./decorators.js" and so it fails
    to resolve.


    [0] https://github.com/rollup/plugins/commit/3d60158f21e0b6a5a8a53d9977928e2e148cb885

    Change-Id: I7829591e45662ee6028182beb57396b327823275
---
 plugins/delete-project | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugins/delete-project b/plugins/delete-project
index 9c4db6de1e..8f6ea7eeb2 160000
--- a/plugins/delete-project
+++ b/plugins/delete-project
@@ -1 +1 @@
-Subproject commit 9c4db6de1e3a00d3f3834ffe0114bd1683f57fb6
+Subproject commit 8f6ea7eeb22f8b8487d3b433d367272172ea32d1
-- 
cgit v1.2.3