Skip to content

Conversation

@erickzhao
Copy link
Member

@erickzhao erickzhao commented Nov 26, 2025

WIP.

Closes #3623
Closes #3684

  • Bump engines to Node 22
  • Update @types/node dependencies
  • Upgrade all @electron/ packages to their latest major versions
  • Use type: module in package.json
  • Drop support Rechoir/Interpret configurations
  • Replace ts-node with tsx
  • Remove dependencies on distutils and Python 3.11
  • Replace lodash with lodash-es
  • Upgrade to Vitest 4
  • Get fast tests to pass
  • Remove Lodash entirely
  • Check if we still need jiti for the configuration loading
  • Check Forge configuration ESM/CJS compatibility
  • Check Webpack plugin ESM/CJS compatibility
  • Check Vite plugin ESM/CJS compatibility
  • Re-enable ESLint import plugin with correct ESM parsing
  • Ensure Forge configurations can still be loaded properly in ESM and CJS
  • Pare down PR into its minimal work product and split off other changes into separate PRs

Split off PRs:

@erickzhao erickzhao added the next label Nov 27, 2025
@erickzhao erickzhao changed the title chore: upgrade major versions to Node 22 chore: Node 22 + ESM Dec 2, 2025
@socket-security
Copy link

socket-security bot commented Dec 4, 2025

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn Medium
Low adoption: npm obug

Location: Package overview

From: ?npm/vitest@4.0.14npm/obug@2.1.1

ℹ Read more on: This package | This alert | What are unpopular packages?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Unpopular packages may have less maintenance and contain other problems.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/obug@2.1.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants