Skip to content

fix: require VS Code 1.103 or later - #69

Open
314systems wants to merge 1 commit into
textlint:mainfrom
314systems:engine
Open

fix: require VS Code 1.103 or later#69
314systems wants to merge 1 commit into
textlint:mainfrom
314systems:engine

Conversation

@314systems

Copy link
Copy Markdown
Contributor

Config file discovery uses fs.globSync, which was added in Node.js v22.0.0 and marked stable in v22.17.0. VS Code 1.100 bundles Node.js 20.19.0 (Electron 34), where fs.globSync does not exist at all, and 1.101/1.102 bundle Node.js 22.15.1, where it still emits an ExperimentalWarning to stderr.

VS Code 1.103 bundles Node.js 22.18.0 (Electron 37), so raise the minimum supported version accordingly.

Config file discovery uses `fs.globSync`, which was added in Node.js
v22.0.0 and marked stable in v22.17.0. VS Code 1.100 bundles Node.js
20.19.0 (Electron 34), where `fs.globSync` does not exist at all, and
1.101/1.102 bundle Node.js 22.15.1, where it still emits an
ExperimentalWarning to stderr.

VS Code 1.103 bundles Node.js 22.18.0 (Electron 37), so raise the
minimum supported version accordingly.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@3w36zj6
3w36zj6 self-requested a review August 29, 2026 08:10
@3w36zj6 3w36zj6 added the Type: Breaking Change Includes breaking changes label Aug 29, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Type: Breaking Change Includes breaking changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants