Skip to content

chore(ci): wasm release #168

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
stormslowly wants to merge 2 commits into from
Closed

chore(ci): wasm release #168

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
091b8a2
refactor: update
stormslowly Mar 5, 2026
216dbf9
fix: wasm binding name
stormslowly Mar 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions napi/index.d.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,6 +194,12 @@ export interface NapiResolveOptions {
* Default `false`
*/
enablePnp?: boolean;
/**
* Path to yarn Plug'n'Play manifest file.
*
* Default `None`
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot Mar 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

In JSDoc for TypeScript, it's more conventional to use undefined to describe the default for an optional property. None is more common in other languages like Rust and might be confusing for JavaScript/TypeScript developers.

Suggested change
* Default `None`
* Default `undefined`

*/
pnpManifest?: string;
}

export interface ResolveResult {
Expand Down
Loading
Loading