DeprecationWarnings

Open
#548 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, nodejs, vscode
Domain
tooling

Research direction

Reproduce the generated extension using the documented npx yo code command and start it in development mode. Inspect the reported extensionHostProcess.js:219 location and compare the output with the listed Buffer(), punycode, and SQLite warnings; done means the reported deprecation warnings are resolved or clearly attributed.

Written by the indexing model from the issue text.

Description

I want to create a vs code extension. Therefore I setup the project like described in the docs:

npx --package yo --package generator-code -- yo code

I started it the first time in dev mode and i get a couple of deprecation warnings:

Here a summary:

  • Buffer() is deprecated due to security and usability issues.
  • The punycode module is deprecated. Please use a userland alternative instead.

Full logs:

(node:47178) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `Code Helper (Plugin) --trace-deprecation ...` to show where the warning was created)
(node:47178) ExperimentalWarning: SQLite is an experimental feature and might change at any time
[INFO] 2026-01-18T20:23:59.032Z - Translations initialized.
[INFO] 2026-01-18T20:23:59.034Z - Extension activated!
(node:47178) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Congratulations, your extension "tangleguard" is now active!

all from extensionHostProcess.js:219

Dominant language
JavaScript
Stars
1.6k
Forks
262
Avg merge
15d 22h
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/vscode-generator-code

All issues in microsoft/vscode-generator-code

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.