custom-elements-everywhere icon indicating copy to clipboard operation
custom-elements-everywhere copied to clipboard

Published 20 hours ago • verified publisher icon webcomponents

Update dependency riot to v7

Open renovate[bot] opened this issue 2 years ago • 0 comments

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
riot (source) 4.14.0 -> 7.1.0 age adoption passing confidence

Release Notes

riot/riot

v7.1.0

Compare Source

v7.0.7

Compare Source

v7.0.6

Compare Source

  • Update improve the deno compatibility adding the file extension to the esm files imports

v7.0.5

Compare Source

  • Improve rendering performance
  • Update development dependencies

v7.0.4

Compare Source

v7.0.3

Compare Source

v7.0.2

Compare Source

v7.0.1

Compare Source

  • Fix small bug computing text expressions in runtime slots

v7.0.0

Compare Source

  • Update: code cleanup to improve the esm bundle and treeshaking
    • Remove: riot.esm.js in favor of the esm folder
  • Add: runtime slots https://github.com/riot/riot/discussions/2917
    • The runtime slots are available in the riot+compiler.js bundle (A documentation update will be available soon)
  • Update: reduced bundle size to 5kb riot.min.js gzipped
  • Update: new Compiler (riot+compiler.js) bundle 50% lighter than the previous one

Important: The documentation will be updated during the next few weeks, however no API breaking changes were introduced.

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

  • Update compiler
    • Components output code will use modern javascript (like arrow functions) reducing heavily their size
    • Components code output will be smaller due to compiler optimizations
  • Update dependencies

v6.0.4

Compare Source

v6.0.3

Compare Source

  • Fix tags with only named export statements. Their javascript will be properly generated also without an export default
  • Update @riotjs/dom-bindings types adding better typescript support

v6.0.2

Compare Source

v6.0.1

Compare Source

  • Update: update the @riotjs/compiler improving the typescript support for type aliases like export type ComponentInterface = RiotComponent<MyComponentProps, MyComponentState>

v6.0.0

Compare Source

If 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

<my-component>
  <p>{ state.greeting }{ props.username }</p>

  <!--
    Notice that lang="ts" does actually nothing.
    It's just needed to let your IDE interpret the below code as typescript.
    The riot compiler will ignore it
  -->
  <script lang="ts">
    import {withTypes, RiotComponent} from 'riot'

    export type MyComponentProps = {
      username: string
    }

    export type MyComponentState = {
      message: string
    }

    export type MyComponent = RiotComponent<MyComponentProps, MyComponentState>

    export default withTypes<MyComponent>({
      state: {
        message: 'hello'
      }
    })
  </script>
</my-component>

Many thanks to https://github.com/kachurun for his help on this major release

v5.4.5

Compare Source

v5.4.4

Compare Source

v5.4.3

Compare Source

v5.4.2

Compare Source

v5.4.1

Compare Source

v5.4.0

Compare Source

  • Update: replace the compiler acorn javascript parser with the (bigger but more modern) @babel/parser
  • Add: typescript syntax support in Riot.js <script> tags

Notice: Riot.js will not type check your components scripts nor transpile them. This version allows you to use the typescript syntax without forcing the use of a typescript preprocessor, but type checking and transpilation should be handled with tools like babel or ts-loader You can check the new compiler here with the following demo component:

<random>
  <h3>{ props.title }</h3>

  <button onclick={ generate }>
    Generate
  </button>

  <h1>
    { state.number }
  </h1>

  <logs logs={ state.logs } onclear={ clearLogs }></logs>

  <script lang="ts">
    import Logs from '../logs/logs.riot'
    import {RandomComponent} from './types'

    function Random(): RandomComponent {
      return {
        state: {
          number: null,
          logs: []
        },
        generate(event: MouseEvent): void {
          this.update({
            number: Math.floor(Math.random() * 10000),
            logs: this.state.logs.concat({
              text: `Generate button clicked. Event type is ${event.type}`
            })
          })
        },
        clearLogs(): void {
          this.update({
            logs: []
          })
        }
      }
    }

    Random.components = {
      Logs
    }

    export default Random
  </script>
</random>

v5.3.3

Compare Source

v5.3.2

Compare Source

v5.3.1

Compare Source

<my-component>
  <p>{ state.message }</p>
  <button onclick={onClick}>Click Me</button>

  <script>
    const context = this

    context.state = {
      message: ''
    }
    
    context.onBeforeMount = () => {
      context.state.message = 'Hello'
    }

    context.onClick = () => {
      context.update({
        message: 'Goodbye'
      })
    }
  </script>
</my-component>

v5.3.0

Compare Source

  • Update improve support for legacy Riot.js syntax fixing some edge cases
  • Update improve support for recursive tags

Now you can recursively render tags without having to register them globally

<recursive-tree>
  <p>{ props.name }</p>
  <recursive-tree 
    if={ props.children.length && props.children } 
    each={ child in props.children } { ...child }/>
</recursive-tree>

v5.2.0

Compare Source

  • Add support for old style Riot.js syntax

Some liked more the old RIot.js syntax so you can now write components also as follows

<old-syntax>
  <p>{ state.message }</p>
  <button onclick={onClick}>Click Me</button>

  <script>
    this.onBeforeMount = () => {
      this.state.message = 'Hello'
    }

    this.onClick = () => {
      this.update({
        message: 'Goodbye'
      })
    }
  </script>
</old-syntax>

v5.1.4

Compare Source

v5.1.3

Compare Source

v5.1.2

Compare Source

  • Update default project branch name master -> main
  • Fix make sure pure components will not be automatically removed by Riot.js if or each directives

v5.1.1

Compare Source

v5.1.0

Compare Source

  • Add support for <template> slot tags https://github.com/riot/riot/issues/2888
  • Add improve debugging support, allowing shortcuts for the use of console methods in expressions: Before {window.console.log('hello')} -> After {console.log('hello')}
  • Improve rendering performance simplifying the compiler output

v5.0.0

Compare 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
  • Replace the internal domdiff rendering engine with a fork of udomdiff
  • Improve rendering performance
  • Improve library size (-1kb)
  • Improve Riot.js is side-effect free. Supports ES2015 exports also, hence fully tree-shakeable
  • Fix https://github.com/riot/riot/issues/2878 browser globals in expressions are available only as window properties breaking change old { 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 becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • [ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate[bot] avatar Aug 02 '22 23:08 renovate[bot]