chore(deps-dev): bump prettier from 2.8.8 to 3.0.1

[dependabot]

Bumps prettier from 2.8.8 to 3.0.1.

Release notes

Sourced from prettier's releases.

3.0.1

🔗 Changelog

3.0.0

diff

🔗 Release note

3.0.0-alpha.6

What's Changed

• Update .d.ts files of plugins to use export default ... by @​fisker in prettier/prettier#14435

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

Full Changelog: prettier/prettier@3.0.0-alpha.5...3.0.0-alpha.6

3.0.0-alpha.5

What's Changed

• Add .d.ts files by @​sosukesuzuki in prettier/prettier#14212
• Support TypeScript 5 via babel-ts parser by @​fisker in prettier/prettier#14391

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

Full Changelog: prettier/prettier@3.0.0-alpha.4...3.0.0-alpha.5

3.0.0-alpha.4

What's Changed

• Remove support for Flow comment types by @​thorn0 in prettier/prettier#13687
• Make resolveParser work like v2 by @​fisker in prettier/prettier#13732
• Add __debug apis to cjs version by @​fisker in prettier/prettier#13731

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

Full Changelog: prettier/prettier@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

Full Changelog: prettier/prettier@3.0.0-alpha.2...3.0.0-alpha.3

3.0.0-alpha.2

• Fix bundled index.cjs file

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

Full Changelog: prettier/prettier@3.0.0-alpha.1...3.0.0-alpha.2

3.0.0-alpha.1

... (truncated)

Changelog

Sourced from prettier's changelog.

3.0.1

diff

Fix cursor positioning for a special case (#14812 by @​fisker)

// <|> is the cursor position
/* Input */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>  } from "fs"
/* Prettier 3.0.0 */
// All messages are represented in JSON.
// So, the prettier.py <|>controls a subprocess which spawns "node {this_file}".
import {} from "fs"
/* Prettier 3.0.1 */
// All messages are represented in JSON.
// So, the prettier.py controls a subprocess which spawns "node {this_file}".
import {<|>} from "fs"

Fix plugins/estree.d.ts to make it a module (#15018 by @​kingyue737)

Add export {} in plugins/estree.d.ts to fix the "File is not a module" error

Add parenthesis around leading multiline comment in return statement (#15037 by @​auvred)

// Input
function fn() {
  return (
    /**
     * @type {...}
     */ expresssion
  )
}
// Prettier 3.0.0
function fn() {
return /**

@​type {...}
*/ expresssion;
}

</tr></table>

... (truncated)

Commits

• afee0db Release 3.0.1
• c3d53dc Fix runYarn function in release script (#15200)
• 825425c chore(deps): update dependency eslint-plugin-import to v2.28.0 (#15184)
• 448217d chore(deps): update dependency eslint to v8.46.0 (#15182)
• f35e9e6 chore(deps): update dependency @​angular/compiler to v16.1.7 (#15173)
• d14e893 chore(deps): update dependency c8 to v8.0.1 (#15174)
• c44d4b7 chore(deps): update dependency eslint-plugin-react to v7.33.1 (#15176)
• 57e8c87 chore(deps): update dependency esbuild to v0.18.17 (#15175)
• 36c3738 chore(deps): update dependency eslint-plugin-unicorn to v48.0.1 (#15177)
• 2d274df chore(deps): update dependency flow-parser to v0.213.1 (#15178)
• Additional commits viewable in compare view

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 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)

[github-actions]

Current branch is dependabot/npm_and_yarn/prettier-3.0.1.
(execution 5758689134 / attempt 1)

[github-actions]

Comment Pull Request - GitHub Actions

What is it ?

A GitHub action that comments with a given message the pull request linked to the pushed branch.
You can even put dynamic data thanks to Contexts and expression syntax.

Usage

Classic usage

on: pull_request

jobs:
  example_comment_pr:
    runs-on: ubuntu-latest
    name: An example job to comment a PR
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Comment PR
        uses: thollander/actions-comment-pull-request@v2
        with:
          message: |
            Hello world ! :wave:

Comment a file content

Thanks to the filePath input, a file content can be commented.
You can either pass an absolute filePath or a relative one that will be by default retrieved from GITHUB_WORKSPACE.
(Note that if both a message and filePath are provided, message will take precedence.)

- name: PR comment with file
  uses: thollander/actions-comment-pull-request@v2
  with:
    filePath: /path/to/file.txt

Setting reactions

You can also set some reactions on your comments through the reactions input.
It takes only valid reactions and adds it to the comment you've just created. (See https://docs.github.com/en/rest/reactions#reaction-types)

- name: PR comment with reactions
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    reactions: eyes, rocket

Specifying which pull request to comment on

You can explicitly input which pull request should be commented on by passing the pr_number input.
That is particularly useful for manual workflow for instance (workflow_run).

...
- name: Comment PR
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    pr_number: 123 # This will comment on pull request #123

Update a comment

Editing an existing comment is also possible thanks to the comment_tag input.

Thanks to this parameter, it will be possible to identify your comment and then to upsert on it.
If the comment is not found at first, it will create a new comment.

That is particularly interesting while committing multiple times in a PR and that you just want to have the last execution report printed. It avoids flooding the PR.

...
- name: Comment PR with execution number
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      _(execution **${{ github.run_id }}** / attempt **${{ github.run_attempt }}**)_
    comment_tag: execution

Note: the input mode can be used to either upsert (by default) or recreate the comment (= delete and create)

Delete a comment

Deleting an existing comment is also possible thanks to the comment_tag input combined with mode: delete.

This will delete the comment at the end of the job.

...
- name: Write a comment that will be deleted at the end of the job
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      The PR is being built...
    comment_tag: to_delete
    mode: delete

Inputs

Action inputs

Name	Description	Required	Default
GITHUB_TOKEN	Token that is used to create comments. Defaults to ${{ github.token }}	✅
message	Comment body
filePath	Path of the file that should be commented
reactions	List of reactions for the comment (comma separated). See https://docs.github.com/en/rest/reactions#reaction-types
pr_number	The number of the pull request where to create the comment		current pull-request/issue number (deduced from context)
comment_tag	A tag on your comment that will be used to identify a comment in case of replacement
mode	Mode that will be used to update comment (upsert/recreate/delete)		upsert
create_if_not_exists	Whether a comment should be created even if comment_tag is not found		true

Permissions

Depending on the permissions granted to your token, you may lack some rights.
To run successfully, this actions needs at least :

permissions: 
   pull-requests: write 

Add this in case you get Resource not accessible by integration error.
See jobs.<job_id>.permissions for more information.

Note that, if the PR comes from a fork, it will have only read permission despite the permissions given in the action for the pull_request event.
In this case, you may use the pull_request_target event. With this event, permissions can be given without issue (the difference is that it will execute the action from the target branch and not from the origin PR).

Contributing

Build

The build steps transpiles the src/main.ts to lib/index.js which is used in a NodeJS environment.
It is handled by vercel/ncc compiler.

$ npm run build

[github-actions]

Content of file referenced with absolute path