tree c4d297c9123d60932fa77fc564f9a03993515eb2
parent 5717badf4250dfe900c05fc00d0758a09ba77297
author Paladox none <thomasmulhall410@yahoo.com> 1654788828 +0000
committer Paladox none <thomasmulhall410@yahoo.com> 1654789756 +0000

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