[Snyk] Upgrade rollup-plugin-typescript2 from 0.24.3 to 0.36.0

[abdulrahman305]

This PR was automatically created by Snyk using the credentials of a real user.


Snyk has created this PR to upgrade rollup-plugin-typescript2 from 0.24.3 to 0.36.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 20 versions ahead of your current version.

• The recommended version was released on 9 months ago.

Release notes

Package name: rollup-plugin-typescript2

• 0.36.0 - 2023-09-27
  

  Features/bugfixes

  • support newer moduleResolution kinds, update build to TS 5.x by @ ezolenko in #453
  • fix: hardcode declaration extension check by @ agilgur5 in #456

  Internal (testing, refactors)

  • github: mark dist/* as generated code by @ agilgur5 in #457
  • deps: auto-update semver via npm audit fix by @ agilgur5 in #459
  • switching from tslint (deprecated) to eslint by @ ezolenko in #463

  Full Changelog: 0.35.0...0.36.0

• 0.35.0 - 2023-06-23
  

  Features

  • Support module: "ES2022" by @ ezolenko in #450
  • Support cts/mts file types by @ ezolenko in #451

  Bugfixes

  • Disable cache in watch mode by @ ezolenko in #452

  Full Changelog: 0.34.1...0.35.0

• 0.34.1 - 2022-10-03
  

  Bugfixes

  • fix: don't error out while catching a buildStart error by @ agilgur5 in #422
    • This fixes an initialization regression in 0.34.0 where users saw TypeError: Cannot read property 'done' of undefined instead of their actual initialization error, such as a tsconfig issue (such as with #421)
  • fix: add compatibility checks w/ semver by @ agilgur5 in #424
    • 0.34.0 introduced a type-only fix that relied on Rollup 2.60.0+ and would (accidentally) error out on older versions of Rollup. This fix handles it gracefully with a clear warning message instead and skips that check when using an older version of Rollup (i.e. partly backward-compatible).
    • This also adds an error if peerDependencies minimum versions have not been met
  • fix: don't resolve filtered files by @ agilgur5 in #428
    • This fixes a regression from 0.33.0 that could cause rpt2 to (accidentally) resolve files that should have been filtered out by the plugin include/exclude (such as with #427)

  Internal (testing, refactors)

  • clean(deps): remove unused @ types/resolve by @ agilgur5 in #423
  • test: increase no-errors integration timeout to 20s by @ agilgur5 in #425

  Full Changelog: 0.34.0...0.34.1

• 0.34.0 - 2022-09-12
  

  Bugfixes

  • fix: handle all type-only imports by piping TS imports by @ agilgur5 in #406
    • If you have ever had issues with some files not being type-checked or not generating declarations, this should conclusively fix all such issues. This type of issue used to occur if you had a type-only / interface-only / emit-less file, i.e. a file with only TS types and interfaces that would produce no JS.
      • For instance: #211, #298, #409, etc
    • NOTE: This requires Rollup version 2.60.0+ as it requires the use of this.load
      • 0.34.0 will (accidentally) error out on older versions of Rollup. 0.34.1 patched this to instead give a warning and skip this check on older versions of Rollup.
  More Fixes ...

  • fix(dx): remove extra quote in emitDeclarationOnly log statement by @ agilgur5 in #412

  Docs

  • docs: add a simple CHANGELOG.md that references GH releases by @ agilgur5 in #419
    • i.e. it references this page

  Internal (testing, refactors)

  • test: ensure declarationMap sources are correct by @ agilgur5 in #403
  • test: add print-diagnostics spec by @ agilgur5 in #405
  More Internal ...

  • refactor(test): heavily simplify the context helper by @ agilgur5 in #404
  • refactor: combine check-tsconfig with parse-tsconfig by @ agilgur5 in #413
  • clean: remove ConsoleContext entirely by using buildStart by @ agilgur5 in #414
  • refactor(cache): simplify creating / using the cache var by @ agilgur5 in #415
  • refactor: consolidate diagnostics funcs into single file by @ agilgur5 in #415

  Full Changelog: 0.33.0.1...0.34.0

• 0.33.0 - 2022-08-19
  
  • similar to the other safety checks in clean, this won't be hit during normal usage
• 0.32.1 - 2022-06-06
  

  Bugfixes

  • deps: upgrade @ rollup/plugin-commonjs to v22 to fix try/catch requires by @ agilgur5 in #340
    • This fixes a regression in 0.32.0 that caused users with certain environments to experience ReferenceError: window is not defined when importing rpt2. See #339

  Full Changelog: 0.32.0...0.32.1

• 0.32.0 - 2022-06-01
  

  Features

  • add rpt2: prefix on more errors by @ ezolenko in ff88951

  Bugfixes

  • fix: normalize paths in get-options-overrides by @ agilgur5 in #331
  • fix: add realpath to host to properly resolve monorepos / symlinks by @ agilgur5 in #332
  • fix: use .d.ts instead of .vue.d.ts for Vue declarations by @ agilgur5 in #336
    • EDIT: Per #224 (comment), this issue and fix seem to have been made erroneously, as the Vue team now mandates .vue.d.ts. As such, this has been reverted in 0.33.0
  • fix: don't attempt to change declarationMap sources when no output by @ agilgur5 in #334
  • fix: force noEmitOnError: false by @ agilgur5 in #338

  Dependencies

  • updating dependencies by @ ezolenko in f84afe9, 0df5362, 5a3e58b, and 08d2f5b
    • EDIT: 08d2f5b caused a regression in certain environments per #339. If you're experiencing ReferenceError: window is not defined, please upgrade to 0.32.1, which should fix this issue.
  • deps: remove unneeded @ types/colors package by @ agilgur5 in #319
  • deps: use normalizePath from @ rollup/pluginutils by @ agilgur5 in #320
  • deps: upgrade tslib to ^2.4.0, remove @ yarn-tool/resolve-package by @ agilgur5 in #326

  Docs

  • fix(docs): _.merge doesn't concat arrays by @ agilgur5 in #314
  • docs: clarify the TS option's defaults by @ agilgur5 in #316
  • docs: split off a CONTRIBUTING.md and improve formatting, grammar, links by @ agilgur5 in #313
  More Docs ...

  • cleaning up badges by @ ezolenko in 4e9f8ff
  • docs: add link to NPM in monthly downloads badge by @ agilgur5 in #318
  • docs: standardize how issues are referenced by @ agilgur5 in #317
  • docs: update Compatibility section with new names and links by @ agilgur5 in #315

  GitHub

  • fix(github): improve formatting of issue template spoilers by @ agilgur5 in #311

  Internal (testing, refactors)

  • test: add initial unit test suite by @ agilgur5 in #321
  • test: 100% coverage in get-options-overrides (createFilter) by @ agilgur5 in #329
  More Internal ...

  • clean: remove partial.ts as this is built into TS by @ agilgur5 in #322
  • optim(ci): use npm ci for install and cache npm by @ agilgur5 in #323
  • ci: add a lint check to ensure all PRs pass lint too by @ agilgur5 in #327
  • refactor: prefer native methods to lodash where possible by @ agilgur5 in #328
  • refactor: invert some conditionals for better readability by @ agilgur5 in #335
  • refactor: sort all top-level imports by @ agilgur5 in #337

  Full Changelog: 0.31.2...0.32.0

• 0.31.2 - 2022-02-01
  

  What's Changed

  • chore: should not lock deps version by @ bluelovers in #293
  • Add trace method to the LanguageServiceHost to enable usage with traceResolution by @ Andarist in #296

  Full Changelog: 0.31.1...0.31.2

• 0.31.1 - 2021-11-23
  

  Fix for #291

  Full Changelog: 0.31.0...0.31.1

• 0.31.0 - 2021-11-17
• 0.30.0 - 2021-02-18
• 0.29.0 - 2020-10-30
• 0.28.0 - 2020-10-16
• 0.27.3 - 2020-09-25
• 0.27.2 - 2020-08-07
• 0.27.1 - 2020-05-12
• 0.27.0 - 2020-03-27
• 0.26.0 - 2020-02-12
• 0.25.3 - 2019-12-03
• 0.25.2 - 2019-11-05
• 0.24.3 - 2019-09-26

from rollup-plugin-typescript2 GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[korbit-ai]

👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: /korbit-review.

As a reminder, here are some helpful tips on how we can collaborate together:

• To have me re-scan your pull request, simply re-invoke the /korbit-review command in a new comment.
• You can interact with me by tagging @korbit-ai in any conversation in your pull requests.
• On any comment I make on your code, please leave a 👍 if it is helpful and a 👎 if it is unhelpful. This will help me learn and improve as we work together
• Lastly, to learn more, check out our Docs.

[codeautopilot]

Your organization has reached the subscribed usage limit. You can upgrade your account by purchasing a subscription at Stripe payment link

Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect.

Current plan usage: 103.59%

Have feedback or need help?
Discord
Documentation
[email protected]

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.