Update dependency @types/chrome to ^0.0.280 #213
Annotations
14 warnings
build (18.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build (18.x):
background-script.js#L107
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (18.x):
background-script.js#L166
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (18.x):
background-script.js#L173
["tabPosition"] is better written in dot notation
|
build (18.x):
background-script.js#L182
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (18.x):
content-script.js#L30
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (18.x):
content-script.js#L31
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (16.x)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-node@v3. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
build (16.x):
background-script.js#L107
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (16.x):
background-script.js#L166
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (16.x):
background-script.js#L173
["tabPosition"] is better written in dot notation
|
build (16.x):
background-script.js#L182
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (16.x):
content-script.js#L30
Prefer using an optional chain expression instead, as it's more concise and easier to read
|
build (16.x):
content-script.js#L31
Prefer using an optional chain expression instead, as it's more concise and easier to read
|