search

bhits / c2s-ui

Consent2Share Consent Management UI by Patient
Apache License 2.0
0 stars 2 forks source link

Failed to run task: 'npm run-script prod' failed #1

Open Nithisha-D opened 6 years ago

Nithisha-D commented 6 years ago 
Hi,

I am trying to build the C2S-UI 3.5.0 version,but it is not build succes, getting "npm run-script prod' failed exception.In package.json file ["c2s-ng-shared": "0.1.0"] dependency is not downloaded from "https://registry.npmjs.org/c2s-ng-shared/-/c2s-ng-shared-0.1.0.tgz".Please help me how to solve that issue.

c2s-ui exce
burcakulug commented 6 years ago

Hi @Nithisha-D, This is a shared Angular component library and unfortunately it has been never published to npm registry. You can build it locally and install from the local build.

  1. Build the library for local use: https://github.com/bhits/c2s-ng-shared#development-build-for-local-use
  2. Install it to c2s-ui from local build: https://github.com/bhits/c2s-ui/blob/master/client/install-local-c2s-ng-shared.sh
Nithisha-D commented 6 years ago

Thank you @burcakulug,

Yes,i cloned and build locally,but still getting the same exception.Please suggest me how to resolve the issue.

Client side error: ERROR in ./src/app/account/account.module.ts Module not found: Error: Can't resolve 'c2s-ng-shared' in 'C:\c2s 3.5.0\c2s-ui-0.8.0\c2s-ui-0.8.0\client\src\app\account' ERROR in ./src/app/account/account-activation/account-activation.component.ts Module not found: Error: Can't resolve 'c2s-ng-shared' in 'C:\c2s 3.5.0\c2s-ui-0.8.0\c2s-ui-0.8.0\client\src\app\account\account-activation' etc..........

Server side error: [ERROR] Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.0:npm (npm run-script prod) on project provider-ui: Failed to run task: 'npm run-script prod' failed. (error code 1) -> [Help 1]

Thank in advance, Nithisha

burcakulug commented 6 years ago

@Nithisha-D , did you also do the second step? that is the one that will make the UI project to use that package from local file system instead of npm registry. based on the errors, it looks like it that package still cannot be resolved.