search

promplate / demo

A simple python server with @promplate. Best practise for prompt engineering applications.
https://demo.promplate.dev/redoc
MIT License
2 stars 1 forks source link

chore(deps-dev): bump @sveltejs/vite-plugin-svelte from 3.1.2 to 4.0.1 in /frontend #221

Closed dependabot[bot] closed 4 days ago

dependabot[bot] commented 1 week ago

Bumps @sveltejs/vite-plugin-svelte from 3.1.2 to 4.0.1.

Release notes

Sourced from @​sveltejs/vite-plugin-svelte's releases.

@​sveltejs/vite-plugin-svelte@​4.0.1

Patch Changes

  • removed references to compiler options no longer available in svelte5 (#1010)

@​sveltejs/vite-plugin-svelte@​4.0.0

Major Changes

  • only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#901)

  • remove support for Svelte 4 (#892)

  • breaking(types): some types that have been unintentionally public are now private (#934)

  • disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)

  • replaced svelte-hmr with Svelte 5 compiler hmr integration (#892)

Minor Changes

  • allow infix notation for svelte modules (#901)

    Previously, only suffix notation .svelte.js was allowed, now you can also use .svelte.test.js or .svelte.stories.js. This helps when writing testcases or other auxillary code where you may want to use runes too.

  • feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#941)

  • feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#989)

Patch Changes

  • fix: make defaultHandler a required argument for onwarn in plugin options (#895)

  • prebundle with dev: true by default (#901)

  • fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#950)

  • fix: ensure svelte modules correctly run in DEV mode (#906)

  • ensure consistent use of compileOptions.hmr also for prebundling (#956)

... (truncated)

Changelog

Sourced from @​sveltejs/vite-plugin-svelte's changelog.

4.0.1

Patch Changes

  • removed references to compiler options no longer available in svelte5 (#1010)

4.0.0

Major Changes

  • only prebundle files with default filenames (.svelte for components, .svelte.(js|ts) for modules) (#901)

  • remove support for Svelte 4 (#892)

  • breaking(types): some types that have been unintentionally public are now private (#934)

  • disable script preprocessing in vitePreprocess() by default because Svelte 5 supports lang=ts out of the box (#892)

  • replaced svelte-hmr with Svelte 5 compiler hmr integration (#892)

Minor Changes

  • allow infix notation for svelte modules (#901)

    Previously, only suffix notation .svelte.js was allowed, now you can also use .svelte.test.js or .svelte.stories.js. This helps when writing testcases or other auxillary code where you may want to use runes too.

  • feat(config): dynamically extract list of svelte exports from peer dependency so that new exports work automatically" (#941)

  • feat(warnings): change default loglevel of warnings originating from files in node_modules to debug. To see them call DEBUG:vite-plugin-svelte:node-modules-onwarn pnpm build. (#989)

Patch Changes

  • fix: make defaultHandler a required argument for onwarn in plugin options (#895)

  • prebundle with dev: true by default (#901)

  • fix(dev): compile with hmr: false for prebundled deps as hmr does not work with that (#950)

... (truncated)

Commits


Dependabot compatibility score

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 rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will 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 version` will 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 dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Chores:

sourcery-ai[bot] commented 1 week ago

Reviewer's Guide by Sourcery

This PR updates the @sveltejs/vite-plugin-svelte dependency from version 3.1.2 to 4.0.1 in the frontend package. This is a major version upgrade that brings significant changes, particularly around Svelte 5 support and removes compatibility with Svelte 4.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Major version upgrade of vite-plugin-svelte with breaking changes
  • Removes support for Svelte 4
  • Integrates with Svelte 5's native TypeScript and HMR support
  • Changes prebundling behavior to only handle default filenames
  • Makes some previously public types private
  • Disables script preprocessing by default
 frontend/package.json
New features and improvements in dependency handling
  • Adds support for infix notation in Svelte module filenames
  • Implements dynamic extraction of Svelte exports from peer dependencies
  • Changes default log level for node_modules warnings to debug
 frontend/package.json
Tips and commands #### Interacting with Sourcery - **Trigger a new review:** Comment `@sourcery-ai review` on the pull request. - **Continue discussions:** Reply directly to Sourcery's review comments. - **Generate a GitHub issue from a review comment:** Ask Sourcery to create an issue from a review comment by replying to it. - **Generate a pull request title:** Write `@sourcery-ai` anywhere in the pull request title to generate a title at any time. - **Generate a pull request summary:** Write `@sourcery-ai summary` anywhere in the pull request body to generate a PR summary at any time. You can also use this command to specify where the summary should be inserted. #### Customizing Your Experience Access your [dashboard](https://app.sourcery.ai) to: - Enable or disable review features such as the Sourcery-generated pull request summary, the reviewer's guide, and others. - Change the review language. - Add, remove or edit custom review instructions. - Adjust other review settings. #### Getting Help - [Contact our support team](mailto:support@sourcery.ai) for questions or feedback. - Visit our [documentation](https://docs.sourcery.ai) for detailed guides and information. - Keep in touch with the Sourcery team by following us on [X/Twitter](https://x.com/SourceryAI), [LinkedIn](https://www.linkedin.com/company/sourcery-ai/) or [GitHub](https://github.com/sourcery-ai).
coderabbitai[bot] commented 1 week ago

[!IMPORTANT]

Review skipped

Bot user detected.

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.

🪧 Tips ### Chat There are 3 ways to chat with [CodeRabbit](https://coderabbit.ai): - Review comments: Directly reply to a review comment made by CodeRabbit. Example: - `I pushed a fix in commit , please review it.` - `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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.` - `@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 using 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. ### Other keywords and placeholders - Add `@coderabbitai ignore` anywhere in the PR description to prevent this PR from being reviewed. - Add `@coderabbitai summary` to generate the high-level summary at a specific location in the PR description. - Add `@coderabbitai` anywhere in the PR title to generate the title automatically. ### CodeRabbit Configuration 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](https://docs.coderabbit.ai/guides/configure-coderabbit) 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](https://docs.coderabbit.ai) for detailed information on how to use CodeRabbit. - Join our [Discord Community](http://discord.gg/coderabbit) to get help, request features, and share feedback. - Follow us on [X/Twitter](https://twitter.com/coderabbitai) for updates and announcements.
dependabot[bot] commented 4 days ago

Superseded by #223.