-
Notifications
You must be signed in to change notification settings - Fork 682
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
fix: remove rimraf from security package #2594
Conversation
|
Performance Test Results The following fails have been reported by WebpageTest. These numbers indicates a possible performance issue with the PR which requires further manual testing to validate. https://pr-2594.pwa-venia.com : LH Performance Expected 0.85 Actual 0.34, LH Accessibility Expected 1 Actual 0.97, LH Best Practices Expected 1 Actual 0.92, WPT Cache Expected 90 Actual 39.333333333333 |
Signed-off-by: sirugh <[email protected]>
@@ -7,20 +7,22 @@ | |||
"description": "Add security headers to UPWARD", | |||
"main": "intercept.js", | |||
"scripts": { | |||
"clean": " " | |||
"clean": "rimraf ./node_modules" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
clean
seems to be more about removing dist
in all other packages. Can we keep this line and just remove the rimraf
dependency entirely?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with either approach, as long as the bug is fixed. Interested in QA outcome.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm - it removes node modules in the gql-queries package
"clean": "rimraf ./lib/magento-compatibility.js ./node_modules",
@@ -7,20 +7,22 @@ | |||
"description": "Add security headers to UPWARD", | |||
"main": "intercept.js", | |||
"scripts": { | |||
"clean": " " | |||
"clean": "rimraf ./node_modules" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm fine with either approach, as long as the bug is fixed. Interested in QA outcome.
Signed-off-by: sirugh <[email protected]>
Description
For some reason
rimraf
as a peer dependency in the upward security headers package was causing odd failures when trying to add a dependency to a package.Moving rimraf to a
devDependency
, or just removing it entirely, fixed the issue.Related Issue
Closes #ISSUE_NUMBER.
Acceptance
Verification Stakeholders
Specification
Verification Steps
yarn install
yarn workspace @magento/venia-concept add -D apollo-link-batch-http
Screenshots / Screen Captures (if appropriate)
Checklist