vaadin-maven-plugin fails on build-frontend

Building a simple Vaadin 14.0.0 project, my build fails with:

21 verbose stack TypeError: Cannot read property ‘resolve’ of undefined 21 verbose stack at regFetch (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/npm-registry-fetch/index.js:76:23) 21 verbose stack at fetchPackument (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:42:10) 21 verbose stack at packument (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetchers/registry/packument.js:20:10) 21 verbose stack at getManifest (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:22:10) 21 verbose stack at manifest (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetchers/registry/manifest.js:13:10) 21 verbose stack at Object.manifest (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetchers/registry/index.js:17:12) 21 verbose stack at Object.Fetcher#manifest [as manifest] (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/node_modules/protoduck/node_modules/genfun/lib/genfun.js:15:38) 21 verbose stack at manifest (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/lib/fetch.js:23:18) 21 verbose stack at pinflight (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/pacote/manifest.js:24:12) 21 verbose stack at /home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/promise-inflight/inflight.js:29:24 21 verbose stack at Promise._execute (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/bluebird/js/release/debuggability.js:313:9) 21 verbose stack at Promise._resolveFromExecutor (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/bluebird/js/release/promise.js:483:18) 21 verbose stack at new Promise (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/bluebird/js/release/promise.js:79:10) 21 verbose stack at _inflight (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/promise-inflight/inflight.js:28:25) 21 verbose stack at /home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/promise-inflight/inflight.js:22:14 21 verbose stack at tryCatcher (/home/k89074/experiment/admin/admin-main/node/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)

during the build-frontend phase. I have tried with installing node v10.16.3 and the latest release.

My package.json file looks fairly simple, too:

{
  "name": "@vaadin/flow-deps",
  "version": "1.0.0",
  "license": "UNLICENSED",
  "dependencies": {
    "@vaadin/vaadin-grid": "5.4.6",
    "@vaadin/vaadin-icons": "4.3.1",
    "@vaadin/vaadin-split-layout": "4.1.1",
    "@vaadin/vaadin-combo-box": "5.0.6",
    "@vaadin/vaadin-core-shrinkwrap": "14.0.0",
    "@vaadin/vaadin-upload": "4.2.2",
    "@vaadin/vaadin-dialog": "2.2.1",
    "@vaadin/vaadin-select": "2.1.5",
    "@vaadin/vaadin-app-layout": "2.0.2",
    "@vaadin/vaadin-item": "2.1.0",
    "@vaadin/vaadin-notification": "1.4.0",
    "@vaadin/vaadin-progress-bar": "1.1.2",
    "@vaadin/vaadin-ordered-layout": "1.1.0",
    "@vaadin/vaadin-login": "1.0.1",
    "@vaadin/vaadin-button": "2.2.1",
    "@vaadin/vaadin-date-picker": "4.0.3",
    "@vaadin/vaadin-text-field": "2.4.8",
    "@vaadin/vaadin-menu-bar": "1.0.3",
    "@vaadin/vaadin-custom-field": "1.0.6",
    "@vaadin/vaadin-form-layout": "2.1.4",
    "@vaadin/vaadin-accordion": "1.0.1",
    "@polymer/iron-list": "3.0.2",
    "@vaadin/vaadin-list-box": "1.1.1",
    "@vaadin/vaadin-details": "1.0.1",
    "@vaadin/vaadin-checkbox": "2.2.10",
    "@polymer/iron-icon": "3.0.1",
    "@vaadin/vaadin-time-picker": "2.0.2",
    "@vaadin/vaadin-context-menu": "4.3.12",
    "@vaadin/vaadin-tabs": "3.0.4",
    "@vaadin/vaadin-radio-button": "1.2.3",
    "@vaadin/vaadin-lumo-styles": "1.5.0",
    "@vaadin/vaadin-material-styles": "1.2.3"
  }
}

I installed node using the suggested way by e.g.

mvn com.github.eirslett:frontend-maven-plugin:1.7.6:install-node-and-npm -DnodeVersion="v12.8.1"

[pleku]

Ok so we’ve been trying to hunt down this and other similar issues. There have been some odd cases when deletion of node_modules, package-lock.json and package.json has been required, but in normal circumstances that should never be required.

Recently we discovered an issue with npm versions 6.11.0-6.11.2 that forced users to delete those files or run npm install manually. That bug has now been fixed in later npm versions and we’ve added a check that fails with clear error message if a faulty npm version is being used.

Since we don’t have any further steps we could take at this point for this ticket and there has not been a response in two weeks, I’m closing this issue. If the problem still reproduces after updating to the latest platform 14.0 maintenance version, please reopen or create a new issue. Cheers

[raphw]

Sorry for the delay, the problem seems to have disappeared with 14.0.10, I did not manage to test it before.