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
2 files changed
tree: c4d297c9123d60932fa77fc564f9a03993515eb2
  1. src/
  2. web/
  3. .bazelignore
  4. .gitignore
  5. BUILD
  7. README.md

Delete project plugin for Gerrit Code Review

A plugin which allows projects to be deleted from Gerrit via an SSH command, REST API or the Project settings screen.

Build Status

JavaScript Plugin Development

For running unit tests execute:

bazel test --test_output=all //plugins/delete-project/web:karma_test

For checking or fixing eslint formatter problems run:

bazel test //plugins/delete-project/web:lint_test
bazel run //plugins/delete-project/web:lint_bin -- --fix "$(pwd)/plugins/delete-project/web"

For testing the plugin with Gerrit FE Dev Helper build the JavaScript bundle and copy it to the plugins/ folder:

bazel build //plugins/delete-project/web:gr-delete-repo
cp -f bazel-bin/plugins/delete-project/web/gr-delete-repo.js plugins/

and let the Dev Helper redirect from .+/plugins/delete-project/static/gr-delete-repo.js to http://localhost:8081/plugins_/gr-delete-repo.js.