search

martinussuherman / vue-template

Vue2 with typescript and vite starter template
https://martinussuherman.github.io/vue-template/
MIT License
22 stars 3 forks source link

Bump prettier from 2.8.7 to 3.1.0 #137

Closed dependabot[bot] closed 11 months ago

dependabot[bot] commented 11 months ago

Bumps prettier from 2.8.7 to 3.1.0.

Release notes

Sourced from prettier's releases.

3.1.0

diff

🔗 Release note

3.0.3

🔗 Changelog

3.0.2

🔗 Changelog

3.0.1

🔗 Changelog

3.0.0

diff

🔗 Release note

3.0.0-alpha.6

What's Changed

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: https://github.com/prettier/prettier/compare/3.0.0-alpha.5...3.0.0-alpha.6

3.0.0-alpha.5

What's Changed

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: https://github.com/prettier/prettier/compare/3.0.0-alpha.4...3.0.0-alpha.5

3.0.0-alpha.4

What's Changed

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: https://github.com/prettier/prettier/compare/3.0.0-alpha.3...3.0.0-alpha.4

3.0.0-alpha.3

  • Fix exports field in package.json file

Other changes since v2, see 3.0.0-alpha.1 release notes

... (truncated)

Changelog

Sourced from prettier's changelog.

3.1.0

diff

🔗 Release Notes

3.0.3

diff

Add preferUnplugged: true to package.json (#15169 by @​fisker and @​so1ve)

Prettier v3 uses dynamic imports, user will need to unplug Prettier when Yarn's PnP mode is enabled, add preferUnplugged: true to package.json, so Yarn will install Prettier as unplug by default.

Support shared config that forbids require() (#15233 by @​fisker)

If an external shared config package is used, and the package exports don't have require or default export.

In Prettier 3.0.2 Prettier fails when attempt to require() the package, and throws an error.

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: No "exports" main defined in <packageName>/package.json

Allow argument of require() to break (#15256 by @​fisker)

// Input
const plugin = require(
  global.STANDALONE
    ? path.join(__dirname, "../standalone.js")
    : path.join(__dirname, "..")
);

// Prettier 3.0.2
const plugin = require(global.STANDALONE
? path.join(__dirname, "../standalone.js")
: path.join(__dirname, ".."));


// Prettier 3.0.3
const plugin = require(
global.STANDALONE
? path.join(__dirname, "../standalone.js")
: path.join(__dirname, "..")
);

Do not print trailing commas in arrow function type parameter lists in ts code blocks (#15286 by @​sosukesuzuki)

... (truncated)

Commits
  • e8ac9f8 Release 3.1.0
  • 6a1d409 chore(deps): update dependency eslint-plugin-regexp to v2 (#15521)
  • f4d93d3 chore(deps): update dependency esbuild to v0.19.5 (#15630)
  • 4fc71a5 chore(deps): update dependency flow-parser to v0.221.0 (#15637)
  • d452f45 chore(deps): update dependency eslint-plugin-jest to v27.6.0 (#15635)
  • eb84a60 chore(deps): update dependency @​types/estree to v1.0.5 (#15625)
  • 2af23ee chore(deps): update dependency webpack to v5.89.0 (#15640)
  • 8f27c73 chore(deps): update dependency eslint-plugin-unicorn to v49 (#15642)
  • cdc5f5a chore(deps): update dependency webpack to v5.89.0 (#15639)
  • 14607ef chore(deps): update dependency eslint-plugin-n to v16.3.1 (#15636)
  • 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 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)
pull-request-quantifier-deprecated[bot] commented 11 months ago

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

dependabot[bot] commented 11 months ago

Superseded by #144.