You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, the unique blocker is the usage of the --experimental-specifier-resolution=node, which starting from Node v19 has been deprecated. To replace it requires the usage of loaders like https://github.com/barhun/extensionless, which enables support to import modules without the file extension. In our case, modules from Buf are using relative imports without file extensions.
The text was updated successfully, but these errors were encountered:
Recently, I noticed how our dependency modules are moving to Node 20. For example: microsoft/vscode-vsce#1035 #1567
Right now, the unique blocker is the usage of the --experimental-specifier-resolution=node, which starting from Node v19 has been deprecated. To replace it requires the usage of loaders like https://github.com/barhun/extensionless, which enables support to import modules without the file extension. In our case, modules from Buf are using relative imports without file extensions.
The text was updated successfully, but these errors were encountered: