Skip to content

Conversation

devversion
Copy link
Member

Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for
automatic retry with cleaned up node modulesbuild: option to
automatically retry postinstall patches

Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for automatic
retry with cleaned up node modules.

Note: Please clean up your node modules after this change. This needs to
still happen manually once, so that we can keep track of applied
patch versions and report/prompt automatically in the future.

@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Jun 11, 2020
@devversion devversion requested a review from a team as a code owner June 11, 2020 20:26
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jun 11, 2020
@devversion
Copy link
Member Author

I wish we'd use TypeScript for this, but it's probably not worth the effort, and the postinstall patches should be somewhat fast.

Here is a link to review this PR with whitespace ignored: https://github.com/angular/components/pull/19615/files?w=1

Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for
automatic retry with cleaned up node modulesbuild: option to
automatically retry postinstall patches

Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for automatic
retry with cleaned up node modules.

Note: Please clean up your node modules after this change. This needs to
still happen manually once, so that we can keep track of applied
patch versions and report/prompt automatically in the future.
@devversion devversion force-pushed the build/postinstall-auto-cleanup branch from fd45213 to 638af9c Compare June 11, 2020 20:34
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@devversion devversion added lgtm action: merge The PR is ready for merge by the caretaker labels Jun 12, 2020
@andrewseguin andrewseguin merged commit d61d94d into angular:master Jun 12, 2020
andrewseguin pushed a commit that referenced this pull request Jun 12, 2020
Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for
automatic retry with cleaned up node modulesbuild: option to
automatically retry postinstall patches

Sometimes we need to change existing postinstall patches. This
requires a cleanup of the currently installed node modules, but
there is no good warning/messaging. We improve this with this
commit by detecting such stale patches and prompting for automatic
retry with cleaned up node modules.

Note: Please clean up your node modules after this change. This needs to
still happen manually once, so that we can keep track of applied
patch versions and report/prompt automatically in the future.
@angular-automatic-lock-bot
Copy link

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

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jul 13, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants