Aha! mystery solved.
.npmrc was pointing to an internal npm registry which couldn't provide the
packages.
Thanks Adam!
On Thu, Jul 11, 2019 at 10:32 AM Adam Peck wrote:
> Do you have any registry overrides in a .npmrc file?
> https://docs.npmjs.com/files/npmrc
>
> On Thu, Jul 11, 2019 at
Do you have any registry overrides in a .npmrc file?
https://docs.npmjs.com/files/npmrc
On Thu, Jul 11, 2019 at 11:21 AM Gian Merlino wrote:
> I haven't seen something like that before. The package version 4.2.6 is
> here on NPM: https://www.npmjs.com/package/@types/react-copy-to-clipboard
>
>
I haven't seen something like that before. The package version 4.2.6 is
here on NPM: https://www.npmjs.com/package/@types/react-copy-to-clipboard
Is it possible your build environment is blocking NPM?
On Thu, Jul 11, 2019 at 9:43 AM Eyal Yurman
wrote:
> The mvn command was actually:
> mvn
The mvn command was actually:
mvn clean install -Pdist -DskipTests, from IntelliJ
(It shouldn't matter though)
On Thu, Jul 11, 2019 at 9:39 AM Eyal Yurman
wrote:
> Hi,
>
> Has anyone encountered the following error?
>
> mvn clean install -PskipTests
>
> [INFO] --- frontend-maven-plugin:1.6:npm
Hi,
Has anyone encountered the following error?
mvn clean install -PskipTests
[INFO] --- frontend-maven-plugin:1.6:npm (npm-install) @ druid-console ---
[INFO] Running 'npm ci' in
/Users/eyurman14/git/yurmix-incubating-druid/web-console
[ERROR] npm ERR! code ETARGET
[ERROR] npm ERR! notarget No