feat: yield new application programming interface
Umbrella API PR. Do not merge or push commits here directly.
We are officially on Node.js 18 now. We have changed the merge requirements accordingly.
You will need to rebase this PR against the main branch OR Click the "Update branch" button to get the new checks going.
Thanks for your contribution.
Socket Security Pull Request Report
👍 No new dependency issues detected in pull request
Pull request report summary
| Issue | Status |
|---|---|
| Install scripts | ✅ 0 issues |
| Native code | ✅ 0 issues |
| Bin script shell injection | ✅ 0 issues |
| Unresolved require | ✅ 0 issues |
| Invalid package.json | ✅ 0 issues |
| HTTP dependency | ✅ 0 issues |
| Git dependency | ✅ 0 issues |
| Potential typo squat | ✅ 0 issues |
| Known Malware | ✅ 0 issues |
| Telemetry | ✅ 0 issues |
| Protestware/Troll package | ✅ 0 issues |
Bot Commands
To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore [email protected] [email protected]
Powered by socket.dev
Let's get this in to avoid all the conflicts with the lock file. The new API will live in its folder, so we should be OK working on the main.
Again to be clear, this is going to be a fast-forward merge, DO NOT land this PR.
And it exploded. Lol. I will take a look.
The tests are failing because jest is picking up the .test.ts files in the API folder; it needs to be ignored for now (if we do not intend on using jest).
@ShaunSHamilton how do you want to proceed?
The tests are failing because
jestis picking up the.test.tsfiles in the API folder; it needs to be ignored for now (if we do not intend on usingjest).@ShaunSHamilton how do you want to proceed?
#49371