**Description:**
I changed the signature of `Resolve` because there was a need to pass the `value` part from `jsc.paths` to the caller.
**Related issue:**
- Closes#8184
**Description:**
Adds a `definite` and `is_override` property to `AutoAccessor` as they were missing.
It also fixes codegen for `AutoAccessor` when emitting TypeScript (which is the main reason I need this PR).
**BREAKING CHANGE:**
Adds a `definite` and `is_override` property.
**Related issue:**
- Closes#8344
**Description:**
The issue was fixed by #8493, but it was not included in the latest release because of the wrong bump comment.
**Related issue:**
- Closes#8491
**Description:**
Currently a jsx pragma with an invalid js identifier (eg, with dashes: `@jsx bad-pragma` causes a panic.
This PR prevents a panic and will ignore an invalid pragma in a comment.
(There may be an argument for showing an error or warning instead, but
given a jsx pragma is still valid ES I'm not sure whether that makes
sense?)
[Original (Deno) issue
here](https://github.com/denoland/deno/issues/21927)
**Description:**
- `swc_common::errors::handler::HANDLER` should be used, and `swc_core::plugin::errors::HANDLER` is now a simple alias.
**Related issue:**
- Closes#8502
**Description:**
I made a bad decision while migrating tests in the core repository to snapshot testing. So, I'm adding the `test!` macro back with a slight renaming.
**Related issue:**
- Closes#8504
**Description:**
For following code
```js
var NaN = 1
console.log(NaN)
```
Result would be
|Envirnoment|Result|
|-|-|
|Non strict script(browser, nodejs repl)|NaN|
|Non strict script(nodejs script)|1|
|Strict script(browser, nodejs repl)|runtime error|
|Strict script(nodejs script)|1|
|ESM|1|
So SWC choose to behave like browser in script mode and confirm to esm
standard.
**Related issue:**
- Closes#8465
