Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps-dev): bump marko from 5.21.2 to 5.29.2 #2401

Merged
merged 1 commit into from
Aug 1, 2023

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Aug 1, 2023

Bumps marko from 5.21.2 to 5.29.2.

Release notes

Sourced from marko's releases.

@​marko/translator-default@​5.29.2

Patch Changes

  • #1999 7957fb564 Thanks @​DylanPiercey! - Switch to .d.marko file for tag types to avoid issues when loaded in a pure typescript project. By default TypeScript doesn't play well with node_modules which are seen as .js files which is what the jsdoc version of a Marko file appears as. By switching to a .d.marko it is instead always seen as .ts which is always analyzed by typescript.

[email protected]

Patch Changes

  • #1999 7957fb564 Thanks @​DylanPiercey! - Switch to .d.marko file for tag types to avoid issues when loaded in a pure typescript project. By default TypeScript doesn't play well with node_modules which are seen as .js files which is what the jsdoc version of a Marko file appears as. By switching to a .d.marko it is instead always seen as .ts which is always analyzed by typescript.

  • Updated dependencies [7957fb564]:

    • @​marko/translator-default@​5.29.2

@​marko/translator-default@​5.29.1

Patch Changes

[email protected]

Patch Changes

@​marko/compiler@​5.29.0

Minor Changes

  • #1980 9d3b34eef Thanks @​DylanPiercey! - Allow parse errors to be recovered from by migrations. This adds a new ast node type of MarkoParseError. MarkoParseError nodes can be removed during the migration stage to handle legacy syntaxes. Any MarkoParseError left in the AST at the end of the migration phase will throw an error similar to what it would have previously thrown synchronously.

    This also means that all parse errors can be surfaced as an aggregate error instead of bailing on the first parse error. When the compiler is ran with errorRecovery: true these errors become diagnostics instead of being thrown.

Patch Changes

@​marko/translator-default@​5.29.0

Minor Changes

  • #1996 d93037843 Thanks @​DylanPiercey! - Move tag validation to the translate phase and expose new utilities for working with macros in @​marko/babel-utils. This allows for migration/transformer/etc compiler hooks to better work with 's.

Patch Changes

... (truncated)

Commits
  • be1cc1b [ci] release
  • 7957fb5 fix: use .d.marko for await tag types
  • 02cea4f [ci] release
  • 2afa3f6 fix: @​marko/register source maps
  • f214d55 [ci] release
  • d930378 feat: move <macro> tag validation to translate stage
  • e8bd325 chore: update test runner to capture diagnostic snapshots
  • 57b280b fix: named component classes deprecate instead of error
  • db141f7 [ci] release
  • 1bc9930 fix: deleting error properties regression
  • Additional commits viewable in compare view

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 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)

Bumps [marko](https://github.com/marko-js/marko) from 5.21.2 to 5.29.2.
- [Release notes](https://github.com/marko-js/marko/releases)
- [Commits](https://github.com/marko-js/marko/compare/[email protected]@5.29.2)

---
updated-dependencies:
- dependency-name: marko
  dependency-type: direct:development
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the 📦 dependencies Pull requests that update a dependency file label Aug 1, 2023
@dependabot dependabot bot requested a review from Romakita August 1, 2023 04:58
@Romakita Romakita merged commit 924c419 into production Aug 1, 2023
35 of 36 checks passed
@Romakita Romakita deleted the dependabot/npm_and_yarn/marko-5.29.2 branch August 1, 2023 11:49
@Romakita
Copy link
Collaborator

🎉 This PR is included in version 7.35.0-beta.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

@Romakita
Copy link
Collaborator

🎉 This PR is included in version 7.34.3 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 dependencies Pull requests that update a dependency file released on @beta released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant