-
Notifications
You must be signed in to change notification settings - Fork 126
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
package.json in the npm package has unwanted IVY metadata #112
Comments
Temporary workaround is to change
and put your active angular version. 8.0.3 in my case at the moment. This is located in ./node-modules/ngx-permissions/package.json |
@monstrege Hi thank You. I will look into it but just to be honest ivy is kinda broken on 8 hopefully will be fixed :-) |
@monstrege - if you were deleting the |
Oh I see that the published |
@petebacondarwin i have rebuild with newest version but its still contains markers
Using angular cli 8.1.0 is it ok?? Or i should change something? |
Don't run |
There should be no such markers in the |
@petebacondarwin Thank You now i understand. When im creating new version it doesn't have ngcc markers. But then im testing that everything works fine in the app and on this moment its adding this markers. |
@monstrege Fix in version 7.0.3 Please can You verify if everything is ok :-) Reopen the issue if there is a problem please :-) |
Cool! |
@AlexKhymenko Thx! |
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
withivy
inangular 8
: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:
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!
The text was updated successfully, but these errors were encountered: