ericclemmons
commented
3 years ago Confirmed that this was a bug in https://unpkg.com/browse/@aws-sdk/middleware-retry@3.6.1/package.json but resolved in https://unpkg.com/browse/@aws-sdk/middleware-retry@3.40.0/package.json.
A PR @aws-amplify/core updated @aws-sdk/client-cloudwatch-logs to ^3.40.0 should resolve this.
/tmp on ☁️ us-east-1
❯ mkdir rn
/tmp on ☁️ us-east-1
❯ cd rn
/tmp/rn on ☁️ us-east-1
❯ git init
/tmp/rn on ☁️ us-east-1
❯ npm init -y
nWrote to /private/tmp/rn/package.json:
{
"name": "rn",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC"
}
╭───────────────────────────────────────────────────────────────╮
│ │
│ New major version of npm available! 6.14.15 → 8.1.3 │
│ Changelog: https://github.com/npm/cli/releases/tag/v8.1.3 │
│ Run npm install -g npm to update! │
│ │
╰───────────────────────────────────────────────────────────────╯
/tmp/rn is 📦 v1.0.0 via ⬢ v14.17.6 on ☁️ us-east-1
❯ npm
/tmp/rn is 📦 v1.0.0 via ⬢ v14.17.6 on ☁️ us-east-1
❯ npm install -g npm
/Users/ecclemm/.nvm/versions/node/v14.17.6/bin/npm -> /Users/ecclemm/.nvm/versions/node/v14.17.6/lib/node_modules/npm/bin/npm-cli.js
/Users/ecclemm/.nvm/versions/node/v14.17.6/bin/npx -> /Users/ecclemm/.nvm/versions/node/v14.17.6/lib/node_modules/npm/bin/npx-cli.js
+ npm@8.1.3
added 70 packages from 18 contributors, removed 289 packages and updated 148 packages in 7.163s
/tmp/rn is 📦 v1.0.0 via ⬢ v14.17.6 on ☁️ us-east-1 took 7s
❯ npm i @aws-amplify/core
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
npm WARN deprecated uglify-es@3.3.9: support for ECMAScript is superseded by `uglify-js` as of v3.13.0
added 772 packages, and audited 773 packages in 26s
19 packages are looking for funding
run `npm fund` for details
31 vulnerabilities (8 moderate, 23 high)
To address all issues, run:
npm audit fix
Run `npm audit` for details.
/tmp/rn is 📦 v1.0.0 via ⬢ v14.17.6 on ☁️ us-east-1 took 26s
❯ npm ls react-native
rn@1.0.0 /private/tmp/rn
└─┬ @aws-amplify/core@4.3.4
└─┬ @aws-sdk/client-cloudwatch-logs@3.6.1
└─┬ @aws-sdk/middleware-retry@3.6.1
└─┬ react-native-get-random-values@1.7.0
└─┬ react-native@0.66.2
└─┬ @react-native-community/cli@6.1.0
└── react-native@0.66.2 deduped
aws-eddy
pelly-ryu
stephenh
armenr
abdallahshaban557
cwomack
Before opening, please confirm:
JavaScript Framework
React
Amplify APIs
Not applicable
Amplify Categories
Not applicable
Environment information
Describe the bug
My project does not nee react-native but it's bring brought in via
@aws-amplify/coreExpected behavior
Maybe declare it as a peer dependency?
Reproduction steps
Install
@aws-amplify/coreCode Snippet
Log output
aws-exports.js
No response
Manual configuration
No response
Additional configuration
No response
Mobile Device
No response
Mobile Operating System
No response
Mobile Browser
No response
Mobile Browser Version
No response
Additional information and screenshots
No response