Issue: Module '@angular/compiler-cli/src/perform_compile' not found while executing ng-packagr

Question

Issue: Module '@angular/compiler-cli/src/perform_compile' not found while executing ng-packagr

I recently installed Windows and am attempting to use ng-packagr for the first time.

Encountering the following error:

Error: Cannot locate module '@angular/compiler-cli/src/perform_compile'
    at Function.Module._resolveFilename (module.js:547:15)
    at Function.Module._load (module.js:474:25)
    at Module.require (module.js:596:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (C:\Users\MyUser\AppData\Roaming\npm\node_modules\ng-packagr\lib\ts\tsconfig.js:3:12)
    at Module._compile (module.js:652:30)
    at Object.Module._extensions..js (module.js:663:10)
    at Module.load (module.js:565:32)
    at tryModuleLoad (module.js:505:12)
    at Function.Module._load (module.js:497:3)

I have already installed Angular CLI by running

npm install -g @angular/cli@latest

Current version is v6.0.8

This is my ng-package.json:

{
    "$schema": "./node_modules/ng-packagr/ng-package.schema.json",
    "lib": {
        "entryFile": "index.ts",
        "externals": {
            "moment": "moment"
        }
    }
}

What could I be overlooking?

npm angular-cli ng-packagr

Answer 1

Answer №1

If you've encountered a similar issue, here's a solution you might want to try:

Start by updating node.js to the latest version (Make sure to uninstall the previous one)

Next, globally install the latest angular-cli version

npm uninstall -g angular-cli
npm cache clean or npm cache verify (if npm > 5)
npm install -g @angular/cli@latest

Create a new project using angular-cli ng new projectname
Transfer your files (modules, components, directives, etc.) from the old project to the newly created one
Install ng-packagr npm i ng-packagr
Update the package.json file in the root of your project
```
"scripts": {
    "packagr": "ng-packagr -p ng-package.json"
}
```
Consider removing dependencies or moving them to peerDependencies if you are creating a feature module

Adjust the ng-package.json file according to your needs

{
  "$schema": "./node_modules/ng-packagr/ng-package.schema.json",
  "lib": {
    "entryFile": "public_api.ts"
  }
}

Update the public_api.ts file with the correct relative path to your module
```
export * from './src/app/modules/yourmodulename/yourmodulename.module
```

After completing these steps, run npm run packagr to generate the dist folder.

You can then publish on npmjs using npm publish dist

This method worked for me and hopefully, it helps you resolve the issue as well.

Answer 2

If you've encountered a similar issue, here's a solution you might want to try:

Start by updating node.js to the latest version (Make sure to uninstall the previous one)

Next, globally install the latest angular-cli version

npm uninstall -g angular-cli
npm cache clean or npm cache verify (if npm > 5)
npm install -g @angular/cli@latest

Create a new project using angular-cli ng new projectname
Transfer your files (modules, components, directives, etc.) from the old project to the newly created one
Install ng-packagr npm i ng-packagr
Update the package.json file in the root of your project
```
"scripts": {
    "packagr": "ng-packagr -p ng-package.json"
}
```
Consider removing dependencies or moving them to peerDependencies if you are creating a feature module

Adjust the ng-package.json file according to your needs

{
  "$schema": "./node_modules/ng-packagr/ng-package.schema.json",
  "lib": {
    "entryFile": "public_api.ts"
  }
}

Update the public_api.ts file with the correct relative path to your module
```
export * from './src/app/modules/yourmodulename/yourmodulename.module
```

After completing these steps, run npm run packagr to generate the dist folder.

You can then publish on npmjs using npm publish dist

This method worked for me and hopefully, it helps you resolve the issue as well.

Issue: Module '@angular/compiler-cli/src/perform_compile' not found while executing ng-packagr

Answer №1

Similar questions

Tips for resolving the out of sync error when deploying a React app to gcloud

Encountering an issue: Module './src/init' not found while attempting to set up a React Native app

Determining the most appropriate time to utilize the 'async' built-in function in ES2017 versus implementing 'npm i async' can depend on a variety of factors such

Babel error: "Issue: Module 'babel-plugin-transform-object-rest-spread' not located within '/vagrant'"

Upgrade the package to the latest major version using NPM

Having trouble accessing the GitHub Package Registry account

Every time I try to install npm, I am bombarded with a massive error log

Discovering the origins of the node.js native modules and delving into the intricacies of typed modules

The proper approach for managing downloaded d.ts files from DefinitelyTyped after installation through npm

Error encountered during yarn installation: Module build has failed due to inability to locate preset "es2015"

Encountered an error stating 'WeakCallbackData' template does not exist in the 'v8' namespace while trying to install npm packages

Angular authentication guard does not redirect properly after returning a Promise<UrlTree>

Is there a way to log into yarn without needing to interact with it manually?

Having trouble installing sqlite3 dependency using npm

Execute Laravel Mix without the need for a system-wide installation of Node.js and npm

When executing `npm run dev` and `npm run start`, a TypeError [ERR_INVALID_ARG_TYPE] is generated along with an [Error: ENOENT: no

Encountering the error message 'No such module' while using npm with node.js on Mac OS X

Encountering a module not found error while accessing Node.js via SSH in Virtualbox

Unable to download packages for a React application

I am receiving no response from the NPM commands whatsoever