Skip to content
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 SDK's peer dependencies versioning #432

Merged
merged 1 commit into from
Mar 1, 2022
Merged

Conversation

vmarta
Copy link
Contributor

@vmarta vmarta commented Feb 26, 2022

Description

Previously the range was matching all possible versions. Now matching React 16 and 17 only.

Related PR #278

Types of Changes

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Documentation update
  • Breaking change (could cause existing functionality to not work as expected)
  • Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

  • Removing a public function or component or prop
  • Adding a required argument to a function
  • Changing the data type of a function parameter or return value
  • Adding a new peer dependency to package.json

How to Test-Drive This PR

# open Node REPL
node

const semver = require('semver')
semver.satisfies('18.0.0', '>=16.14 <18')  #return false
semver.satisfies('17.0.0', '>=16.14 <18')  #return true

Checklists

General

  • Changes are covered by test cases
  • CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

  • There are no changes to UI

or...

Localization

  • Changes include a UI text update in the Retail React App (which requires translation)

Previously the range was matching all possible versions. Now matching React 16 and 17 only.
@vmarta vmarta requested a review from a team as a code owner February 26, 2022 08:07
Comment on lines -160 to +161
"react": ">=16.14 || <18",
"react-dom": ">=16.14 || <18",
"react": ">=16.14 <18",
"react-dom": ">=16.14 <18",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

Previously, 20.0.0 was matched with >=16.14, while 1.0.0 was matched with <18.

@vmarta vmarta added the ready for review PR is ready to be reviewed label Feb 26, 2022
Copy link
Contributor

@vcua-mobify vcua-mobify left a comment

Choose a reason for hiding this comment

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

+1

@vmarta vmarta merged commit e4a5bff into develop Mar 1, 2022
@vmarta vmarta deleted the fix-peer-dependencies branch March 1, 2022 18:24
adamraya added a commit that referenced this pull request Mar 22, 2022
* Fix SDK's peer dependencies versioning (#432)

Previously the range was matching all possible versions. Now matching React 16 and 17 only.

* Node warnings with better version formatting (#410)

The node version range is now taken from the engines field of the package.json, which is more readable than seeing semver's representation (>=12.0.0 <13.0.0-0||>=14.0.0 <15.0.0-0).

* [Circle CI] Add test generated project job on Windows (#412)

* Update config.yml

* Add `generatedSFCCProjectTestWindows` test job

* Test not using gtime.js script

* Increase log verbosity

* Run first the CI job generated project on Windows

* Use  outputDir generated-project

* Use execSync

* Update npx pwa-kit-create-app command

* Use process.argv as outputDir

* Test execFileSync

* Add try/catch to execSync

* Show npm i logging

* Show npm install logs as we do in the BFH branch

* Show verdaccio logs

* More logs npm install verbose

* Use Node child_process & Update verdaccio config & bump version

* Use verdaccio npmjs cache true

* Set GENERATOR_PRESET env variable

* Update create-mobify-app.js

* Test using a xlarge Windows machine

* Increase Verdaccio max_fails config

* Remove server keepAliveTimeout

* Dump all Verdaccio logs to a file for debugging

* Fix smoketestscripts on Windows

* Add Circle CI unit to the scripts path

* Really fix smoketestscripts Circle CI job on Windows

* Update config.yml

* More testing smoke test script on Windows

* And more testing smoke test script on Windows

* smoketestscripts job working on Windows

* fix typo

* Clean up

* More clean up

* Update latest v4 verdaccio

* Remove file from bad merge

Co-authored-by: Vincent Marta <vmarta@salesforce.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready for review PR is ready to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants