search

ZFGCCP / ZFGCBB-React

front end for zfgcbb
2 stars 0 forks source link

chore(deps): bump @linaria/core from 4.5.4 to 6.2.0 #10

Closed dependabot[bot] closed 3 weeks ago

dependabot[bot] commented 3 weeks ago

Bumps @linaria/core from 4.5.4 to 6.2.0.

Release notes

Sourced from @​linaria/core's releases.

@​linaria/core@​6.2.0

Minor Changes

  • a3dcee2e: Update wyw-in-js to 0.5.3

@​linaria/core@​6.1.0

Minor Changes

Patch Changes

  • 8d4ebd33: chore: bump @wyw-in-js/* packages

@​linaria/core@​6.0.0

Major Changes

  • 2ac94b99: BREAKING CHANGE: Linaria has been migrated to wyw-in-js.

    Migration Guide

    For Users

    The main breaking change is that all tooling has been moved from the @linaria scope to the @wyw-in-js scope. This means that you will need to update your dependencies as follows:

    Old New
    @​linaria/babel-preset @​wyw-in-js/babel-preset
    @​linaria/cli @​wyw-in-js/cli
    @​linaria/esbuild @​wyw-in-js/esbuild
    @​linaria/rollup @​wyw-in-js/rollup
    @​linaria/shaker discontinued
    @​linaria/vite @​wyw-in-js/vite
    @​linaria/webpack4-loader discontinued
    @​linaria/webpack5-loader @​wyw-in-js/webpack-loader

    There is no longer a need to install @linaria/shaker as it is now part of @wyw-in-js/transform, which will be installed automatically with the bundler plugins.

    The configuration file has been renamed from linaria.config.js (linariarc) to wyw-in-js.config.js (.wyw-in-jsrc).

    For Custom Processor Developers

    Base classes for processors and most helpers have been moved to @wyw-in-js/processor-utils.

    All APIs that had linaria in their names have been renamed:

    • The field that stores meta information in runtime has been renamed from __linaria to __wyw_meta
    • The export with all interpolated values has been renamed from __linariaPreval to __wywPreval
    • The caller name in Babel has been renamed from linaria to wyw-in-js

... (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)
gm112 commented 3 weeks ago

I enabled "type": "module" in https://github.com/ZFGCCP/ZFGCBB-React/blob/de40302bf8a057da428486d8abab5223a5a2f9b4/package.json#L4 because of https://vitejs.dev/guide/troubleshooting.html#vite-cjs-node-api-deprecated

gm112 commented 3 weeks ago

Please note that this will require a yarn install on your machine when the merge happens!