Several properties in TypeScript types for Config should be made optional

[cspotcode]

Describe the bug

TypeScript types for AmdConfig mark moduleId as required; should be optional.

The type is declared are required here:

swc/node-swc/src/types.ts

Line 579 in ebdd04d

moduleId: string;

It is documented as optional here:
https://swc.rs/docs/swcrc-module#amd

EDIT I believe that a few more should also be made optional:

swc/node-swc/src/types.ts

Lines 407 to 456 in ebdd04d

	export interface ReactConfig {
	/**
	* Replace the function used when compiling JSX expressions.
	*
	* Defaults to `React.createElement`.
	*/
	pragma: string;
	/**
	* Replace the component used when compiling JSX fragments.
	*
	* Defaults to `React.Fragment`
	*/
	pragmaFrag: string;
	/**
	* Toggles whether or not to throw an error if a XML namespaced tag name is used. For example:
	* `<f:image />`
	*
	* Though the JSX spec allows this, it is disabled by default since React's
	* JSX does not currently have support for it.
	*
	*/
	throwIfNamespace: boolean;
	/**
	* Toggles plugins that aid in development, such as @swc/plugin-transform-react-jsx-self
	* and @swc/plugin-transform-react-jsx-source.
	*
	* Defaults to `false`,
	*
	*/
	development: boolean;
	/**
	* Use `Object.assign()` instead of `_extends`. Defaults to false.
	*/
	useBuiltins: boolean;
	/**
	* Enable fast refresh feature for React app
	*/
	refresh: boolean;
	/**
	* jsx runtime
	*/
	runtime: 'automatic' | 'classic'
	/**
	* Declares the module specifier to be used for importing the `jsx` and `jsxs` factory functions when using `runtime` 'automatic'
	*/
	importSource: string
	}

ReactConfig: importSource, refresh, runtime

Input code

N/A

Config

N/A

Expected behavior

Typechecking should pass when omitting moduleId from module config object.

Version
The version of @swc/core: master branch on github

[cspotcode]

I updated the title and edited the issue description to include some additional config properties which I believe should be made optional as well.

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.