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): update all non-major dependencies #108

Merged
merged 1 commit into from May 29, 2022
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 29, 2022

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
esbuild ^0.14.41 -> ^0.14.42 age adoption passing confidence
pnpm (source) 7.1.6 -> 7.1.7 age adoption passing confidence
vitest ^0.12.9 -> ^0.13.0 age adoption passing confidence

Release Notes

evanw/esbuild

v0.14.42

Compare Source

  • Fix a parser hang on invalid CSS (#​2276)

    Previously invalid CSS with unbalanced parentheses could cause esbuild's CSS parser to hang. An example of such an input is the CSS file :x(. This hang has been fixed.

  • Add support for custom log message levels

    This release allows you to override the default log level of esbuild's individual log messages. For example, CSS syntax errors are treated as warnings instead of errors by default because CSS grammar allows for rules containing syntax errors to be ignored. However, if you would like for esbuild to consider CSS syntax errors to be build errors, you can now configure that like this:

    • CLI

      $ esbuild example.css --log-override:css-syntax-error=error
    • JS API

      let result = await esbuild.build({
        entryPoints: ['example.css'],
        logOverride: {
          'css-syntax-error': 'error',
        },
      })
    • Go API

      result := api.Build(api.BuildOptions{
        EntryPoints: []string{"example.ts"},
        LogOverride: map[string]api.LogLevel{
          "css-syntax-error": api.LogLevelError,
        },
      })

    You can also now use this feature to silence warnings that you are not interested in. Log messages are referred to by their identifier. Each identifier is stable (i.e. shouldn't change over time) except there is no guarantee that the log message will continue to exist. A given log message may potentially be removed in the future, in which case esbuild will ignore log levels set for that identifier. The current list of supported log level identifiers for use with this feature can be found below:

    JavaScript:

    • assign-to-constant
    • call-import-namespace
    • commonjs-variable-in-esm
    • delete-super-property
    • direct-eval
    • duplicate-case
    • duplicate-object-key
    • empty-import-meta
    • equals-nan
    • equals-negative-zero
    • equals-new-object
    • html-comment-in-js
    • impossible-typeof
    • private-name-will-throw
    • semicolon-after-return
    • suspicious-boolean-not
    • this-is-undefined-in-esm
    • unsupported-dynamic-import
    • unsupported-jsx-comment
    • unsupported-regexp
    • unsupported-require-call

    CSS:

    • css-syntax-error
    • invalid-@​charset
    • invalid-@​import
    • invalid-@​nest
    • invalid-@​layer
    • invalid-calc
    • js-comment-in-css
    • unsupported-@​charset
    • unsupported-@​namespace
    • unsupported-css-property

    Bundler:

    • different-path-case
    • ignored-bare-import
    • ignored-dynamic-import
    • import-is-undefined
    • package.json
    • require-resolve-not-external
    • tsconfig.json

    Source maps:

    • invalid-source-mappings
    • sections-in-source-map
    • missing-source-map
    • unsupported-source-map-comment

    Documentation about which identifiers correspond to which log messages will be added in the future, but hasn't been written yet. Note that it's not possible to configure the log level for a build error. This is by design because changing that would cause esbuild to incorrectly proceed in the building process generate invalid build output. You can only configure the log level for non-error log messages (although you can turn non-errors into errors).

pnpm/pnpm

v7.1.7

Compare Source

Patch Changes

  • Improve the performance of the build sequence calculation step #​4815.
  • Correctly detect repeated dependency sequence during resolution #​4813.

Our Sponsors

#### What's Changed * fix: `pnpm add @​teambit/bit` should succeed by @​zkochan in https://github.com/pnpm/pnpm/pull/4813 * perf: build-modules by @​zkochan in https://github.com/pnpm/pnpm/pull/4815

Full Changelog: pnpm/pnpm@v7.1.6...v7.1.7

vitest-dev/vitest

v0.13.0

Compare Source

Features

v0.12.10

Compare Source

Bug Fixes
Features

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, click this checkbox.

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

@antfu antfu merged commit 537a712 into main May 29, 2022
@antfu antfu deleted the renovate/all-minor-patch branch May 29, 2022 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants