Update git submodules
* Update plugins/delete-project from branch 'stable-3.8'
to 9378a0e55daf9e24b8863a2605e6a1f1828f73a1
- Merge branch 'stable-3.7' into stable-3.8
* stable-3.7:
Add support for newer plugin-node-resolve versions
Change-Id: Ie731df59db447bd619a2151b7ffbd371cff1bf31
- 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
diff --git a/plugins/delete-project b/plugins/delete-project
index 825dcb4..9378a0e 160000
--- a/plugins/delete-project
+++ b/plugins/delete-project
@@ -1 +1 @@
-Subproject commit 825dcb41a9abfc5892ef3b0f8e89b7ca25c8dfe1
+Subproject commit 9378a0e55daf9e24b8863a2605e6a1f1828f73a1
