Skip to content
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.

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

Use node:buffer explicitly #835

Merged
merged 2 commits into from
May 7, 2024
Merged

Conversation

Yang-33
Copy link
Contributor

@Yang-33 Yang-33 commented May 1, 2024

While it works without explicit node:buffer in a Node.js environment, it won't work in environments compatible with Node.js. There's no downside to explicitly using node:buffer. This change supports that.

@Yang-33 Yang-33 marked this pull request as ready for review May 1, 2024 12:08
@Yang-33 Yang-33 requested review from mokuzon and habara-k May 1, 2024 12:09
@Yang-33 Yang-33 enabled auto-merge (squash) May 1, 2024 12:09
@@ -47,7 +47,6 @@
"docs:preview": "vitepress preview docs",
"docs:deploy": "./scripts/deploy-docs.sh",
"apidocs": "typedoc --excludePrivate --plugin typedoc-plugin-markdown --out docs/apidocs lib/index.ts",
"generate-changelog": "ts-node ./scripts/generate-changelog.ts",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

it's no longer necessary now

@@ -19,7 +19,7 @@
"types": "./dist/cjs/index.d.ts",
"default": "./dist/cjs/index.js"
},
"default": "./dist/cjs/index.js"
"default": "./dist/cjs/index.js"
Copy link
Contributor Author

Choose a reason for hiding this comment

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

(format)

@Yang-33 Yang-33 merged commit f986b45 into line:master May 7, 2024
3 checks passed
@Yang-33 Yang-33 deleted the use-node-buffer-explicitly branch May 7, 2024 14:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants