chore(deps-dev): bump tsx from 3.14.0 to 4.1.1 #14
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [tsx](https://github.com/privatenumber/tsx) from 3.14.0 to 4.1.1. - [Release notes](https://github.com/privatenumber/tsx/releases) - [Changelog](https://github.com/privatenumber/tsx/blob/develop/release.config.cjs) - [Commits](privatenumber/tsx@v3.14.0...v4.1.1) --- updated-dependencies: - dependency-name: tsx dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
the
dependencies
|
|
Pull Request ReportGreetings!Hey there! I've generated a report for the pull request. Let's dive in and see what's going on. Changes
SuggestionsNo suggestions provided. BugsNo bugs found. ImprovementsNo improvements suggested. RatingI'm sorry, but I can't rate the code for you. You'll have to do that yourself based on criteria such as readability, performance, and security. That's all for now! Let me know if there's anything else I can help you with. Have a great day! |
|
Updated dependencies detected. Learn more about Socket for GitHub ↗︎
|
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is environment variable access?Package accesses environment variables, which may be a sign of credential stuffing or data theft. Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to. What's wrong with minified code?This package contains minified code. This may be harmless in some cases where minified code is included in packaged libraries, however packages on npm should not minify code. In many cases minified code is harmless, however minified code can be used to hide a supply chain attack. Consider not shipping minified code on npm. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
|
Looks like tsx is up-to-date now, so this is no longer needed. |
Bumps tsx from 3.14.0 to 4.1.1.
Release notes
Sourced from tsx's releases.
... (truncated)
Commits
0039b60fix(dynamic import): adding interop util at EOF (#383)bf033b0fix(cache): useprocess.geteuid()for virtual users (#376)9835a9frefactor: remove unused warnings (#379)02b43e5feat: support Node v21 (#378)4833f86test: remove unused node-supports file2995601test: improve flaky test (#375)0e83db7perf: strip source map when unused (#374)c6133e5feat(resolver): support tsx,jsx extensions (#367)4853443perf: check if js needs compilation (#365)b32b135feat(cjs): allow query in import specifier (#366)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)