commit 99e8ad00012db78e310c086f0cea8d1215844f6a
author Paladox none <thomasmulhall410@yahoo.com> Tue Feb 27 20:24:22 2024 +0000
committer Gerrit Code Review <noreply-gerritcodereview@google.com> Tue Feb 27 20:24:22 2024 +0000
tree 634208e444c72da9e7b16309d8bd6599ad39a845
parent 662f6cffa24b3d442e5eddf95d3f12154495bf7c

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