summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDaniele Sassoli <danielesassoli@gmail.com>2024-03-01 17:16:06 +0000
committerGerrit Code Review <noreply-gerritcodereview@google.com>2024-03-01 17:16:06 +0000
commit87c9778e87de232c1e62abd5dc82fdbbf6b56f9b (patch)
tree885bbbbeba63f08be05a2f34af09945d0825ac81
parentcffab2932238b69b8d7a711c569bf772e7fb3799 (diff)
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
m---------plugins/delete-project0
1 files changed, 0 insertions, 0 deletions
diff --git a/plugins/delete-project b/plugins/delete-project
-Subproject 825dcb41a9abfc5892ef3b0f8e89b7ca25c8dfe
+Subproject 9378a0e55daf9e24b8863a2605e6a1f1828f73a