question-mark

Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

package.json in the npm package has unwanted IVY metadata

See original GitHub issue

Issue Description

Hi,

I finally figured what a bug I was experiencing since a few days was.

I was getting this when I was trying to ng build --prod with ivy in angular 8 :

ERROR in The ngcc compiler has changed since the last ngcc build.
Please completely remove `node_modules` and try again.

which I did many times without success…

I finally found out that the culprit was the ngx-permission package.json that has some ivy compiler metadata inside.

Especially this part:

"__processed_by_ivy_ngcc__": {
    "fesm2015": "8.0.0",
    "typings": "8.0.0",
    "fesm5": "8.0.0",
    "es2015": "8.0.0",
    "esm2015": "8.0.0",
    "esm5": "8.0.0",
    "module": "8.0.0"
  },

This part should just be local data, and not be something included in the npm package. (from my too small knowledge about it)

I’m not blaming anyone here 😃

I just don’t think that the ivy compiler should change the file and add some garbage metadata inside the package.json like that.

Can anyone remove the __processed_by_ivy_ngcc__ part from the npm package?

Thanks alot!

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:11 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
monstregecommented, Jul 8, 2019

@AlexKhymenko Thx! Also, I believe that those tags will be ok when ivy will work, but not at the moment. EDIT: It works well now 😃

1reaction
petebacondarwincommented, Jul 8, 2019

Oh I see that the published package.json file does indeed have these markers!! https://unpkg.com/ngx-permissions@7.0.2/package.json

Read more comments on GitHub >

github_iconTop Results From Across the Web

Node dependency package.json metadata changing over time ...
The homepage field is set from the github url when normalize-package-data is run. This is not consistently happening when you do the install...
Read more >
Build Times, Bundle Sizes, and Other Improvements Made by ...
This article covers Ivy, Angular's next-gen compilation pipeline, and the new and exciting improvements that came with the Version 9 ...
Read more >
Angular package format
The primary package.json contains important package metadata, including the following: It declares the package to be in EcmaScript Module (ESM) format.
Read more >
Artifactory Release Notes - JFrog - JFrog Documentation
Fixed an issue whereby, NuGet search queries failed when searching for packages with unencoded characters in the package metadata URL fields. RTFACT-26945.
Read more >
Documentation (2.0.0) | Apache Ivy™
To find these metadata and your dependencies artifacts (usually jars), Ivy can be ... All of the Ivy Java package names have changed...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found