**Description:**
From the typescript
[baseUrl](https://www.typescriptlang.org/docs/handbook/modules/reference.html#baseurl)
doc: When using bare specifiers (module specifiers that don’t begin with
./, ../, or /), baseUrl has a higher precedence than node_modules
package lookups.
In the current tsc resolver implementation, when resolving bare module
specifiers, baseUrl was not used except for `paths`, this cause the
belowing resolution failed, but it worked when used in typescript
project.
`tsconfig.json` / `.swcrc`:
```json
{
baseUrl: "."
paths: {
"@common/*": ["src/common/*"]
}
}
```
File structure:
- ./src/common/helper.ts
- ./src/index.ts
./src/index.ts content:
```ts
// tsc can resolve this, but tsc resolver cannot
import sth from "src/common/helper"
```
**Description:**
- This PR fixes the source map generation when `inputSourceMap` is specified.
- This PR fixes `minify()` not accepting parsed source map in the option.
**Related issue:**
- Closes#8372.
**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)
