Skip to content
This repository has been archived by the owner on Apr 9, 2021. It is now read-only.

npm prune is not now run when building #98

Merged
merged 1 commit into from Jan 14, 2020
Merged

npm prune is not now run when building #98

merged 1 commit into from Jan 14, 2020

Conversation

grossmannmartin
Copy link
Member

Q A
Description, reason for the PR NPM prune fails because of npm/cli#613 and Travis fails on this. This PR removes npm prune from npm phing target as it's not necessary to run it anyway
New feature No
Fixes issues ...
Have you read and signed our License Agreement for contributions? Yes

@sonarcloud
Copy link

sonarcloud bot commented Jan 14, 2020

Kudos, SonarCloud Quality Gate passed!

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities (and Security Hotspot 0 Security Hotspots to review)
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

@grossmannmartin grossmannmartin merged commit 5cb9e15 into master Jan 14, 2020
@grossmannmartin grossmannmartin deleted the mg-hotfix-npm branch January 14, 2020 08:51
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@pesektomas pesektomas pesektomas approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
2 participants
@grossmannmartin @pesektomas