-
Notifications
You must be signed in to change notification settings - Fork 108
Update dependency riot to v9 #2295
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
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
6ddd664 to
4db324d
Compare
4db324d to
7cd881f
Compare
7cd881f to
25ca966
Compare
a9cfe49 to
df11b4f
Compare
f28fda4 to
6676691
Compare
6676691 to
55d7587
Compare
b1d1d79 to
35c852e
Compare
0dcde4c to
80476c6
Compare
80476c6 to
759d987
Compare
759d987 to
226a986
Compare
d103c84 to
6e1da55
Compare
d1a68bf to
8fb66b1
Compare
9dcbd5c to
e981aa6
Compare
28eddff to
94dd639
Compare
f7ecf24 to
fb65277
Compare
fb65277 to
359c1b3
Compare
d88f87e to
e03c877
Compare
e03c877 to
5f68feb
Compare
2a1c97d to
c78630d
Compare
c78630d to
7e77431
Compare
4ad111b to
414d5a2
Compare
414d5a2 to
44dd718
Compare
Collaborator
|
Out of date. |
auto-merge was automatically disabled
August 6, 2025 13:29
Pull request was closed
Contributor
Author
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.14.0->9.4.11Release Notes
riot/riot (riot)
v9.4.11Compare Source
v9.4.10Compare Source
v9.4.9Compare Source
v9.4.8Compare Source
v9.4.7Compare Source
v9.4.6Compare Source
refAPIv9.4.5Compare Source
withTypesmethod https://github.com/riot/riot/issues/3046v9.4.4Compare Source
v9.4.3Compare Source
v9.4.2Compare Source
mainbranch will be used for development and releasesv9.4.1Compare Source
v9.4.0Compare Source
refattributes https://github.com/riot/riot/issues/3015v9.3.0Compare Source
v9.2.2Compare Source
v9.2.1Compare Source
v9.2.0Compare Source
v9.1.8Compare Source
v9.1.7Compare Source
v9.1.6Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
v9.1.3Compare Source
v9.1.2Compare Source
@riotjs/dom-bindingstypesv9.1.1Compare Source
exportskeys in thepackage.jsonfilev9.1.0Compare Source
v9.0.4Compare Source
v9.0.3Compare Source
inputorselectv9.0.2Compare Source
>=18.0.0value inpackage.jsonv9.0.1Compare Source
v9.0.0: EvergreenCompare Source
V9 is almost fully backward compatible with previous versions of Riot.js. However, a few breaking changes have been made, which are listed below:
nullorundefined(see also https://github.com/riot/riot/issues/2975). For example:<p is-active={false}>-is-activewill no longer be removed. Use<p is-active={null}>insteadcheckedorselectedand in that case remove them with falsy valuesSeveral ecosystem packages have received major updates and the rest will be updated soon. Future versions of Riot.js ecosystem packages will be synchronized to avoid confusion. To use Riot.js v9, ensure that you install only v9 @riotjs packages.
v7.1.0Compare Source
v7.0.7Compare Source
riot.versionwrong value in theesmexportv7.0.6Compare Source
esmfiles importsv7.0.5Compare Source
v7.0.4Compare Source
v7.0.3Compare Source
v7.0.2Compare Source
v7.0.1Compare Source
v7.0.0Compare Source
esmbundle and treeshakingriot.esm.jsin favor of theesmfolderslotshttps://github.com/riot/riot/discussions/2917riot+compiler.jsbundle (A documentation update will be available soon)Important: The documentation will be updated during the next few weeks, however no API breaking changes were introduced.
v6.1.2Compare Source
v6.1.1Compare Source
v6.1.0Compare Source
v6.0.4Compare Source
v6.0.3Compare Source
@riotjs/dom-bindingstypes adding better typescript supportv6.0.2Compare Source
v6.0.1Compare Source
@riotjs/compilerimproving the typescript support for type aliases like export type ComponentInterface = RiotComponent<MyComponentProps, MyComponentState>v6.0.0Compare Source
slotshttps://github.com/riot/riot/issues/2920If you are not a typescript user this release doesn't introduce any braking change. If you are a typescript user you can start writing Riot.js components as follows
Many thanks to https://github.com/kachurun for his help on this major release
v5.4.5Compare Source
v5.4.4Compare Source
v5.4.3Compare Source
v5.4.2Compare Source
mountandunmounttype declarations https://github.com/riot/riot/pull/2909 @kachurunv5.4.1Compare Source
v5.4.0Compare Source
acornjavascript parser with the (bigger but more modern)@babel/parser<script>tagsNotice:
Riot.js will not type check your components scripts nor transpile them. This version allows you to use the
typescriptsyntax without forcing the use of a typescript preprocessor, but type checking and transpilation should be handled with tools likebabelorts-loaderYou can check the new compiler here with the following demo component:
v5.3.3Compare Source
v5.3.2Compare Source
v5.3.1Compare Source
v5.3.0Compare Source
Now you can recursively render tags without having to register them globally
v5.2.0Compare Source
Some liked more the old RIot.js syntax so you can now write components also as follows
v5.1.4Compare Source
<template>fragments https://github.com/riot/riot/issues/2892v5.1.3Compare Source
v5.1.2Compare Source
master->mainiforeachdirectivesv5.1.1Compare Source
v5.1.0Compare Source
<template>slot tags https://github.com/riot/riot/issues/2888consolemethods in expressions: Before{window.console.log('hello')}-> After{console.log('hello')}v5.0.0Compare Source
This release is completely backward compatible, make sure to update the
@riotjs/[email protected]along with[email protected]. All the Riot.js echosystem tools should keep working as expected without needing major release updates.Changelog
windowproperties breaking changeold
{ location.href }new{ window.location.href }Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.