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.

Angular 13 - Option to remove prepublishOnly script

See original GitHub issue

Type of Issue

[ ] Bug Report
[x] Feature Request

Description

Now that Angular 13 has been released, and ViewEngine is deprecated, can we please revisit the request to remove the prepublishOnly script? I’m publishing a private repo to npm that will only be consumed by Ivy applications. I know that there are workarounds to remove or ignore the script, but it would be nice to not have to do this anymore

Expected Behaviour

Add a flag or something to opt out of the prepublishOnly script

Issue Analytics

State:
Created 2 years ago
Reactions:2
Comments:8 (5 by maintainers)

Top GitHub Comments

1reaction

JoostKcommented, Nov 16, 2021

So if I understand correctly, the problem is that my library being built in “partial” mode is actually showing something that I should have fixed a long time ago? (the cyclical dependencies).

The constraint around cyclic dependencies is new to Ivy, please see https://github.com/angular/angular/issues/43227#issuecomment-904173738 for background information.

Apart from the building libraries section on angular.io, are there any other official resources of how to go about resolving these cyclical dependency issues? Is the major problem mainly components used in other components? It’s proving quite the undertaking for my team.

There are some hints to avoid the cycles in the NG3003 error documentation page.

0reactions

github-actions[bot]commented, Dec 18, 2021

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

_{This action has been performed automatically by a bot.}