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
What version of this package are you using?
v2.1.0
What operating system, Node.js, and npm version?
I am getting the same errors on both Arch Linux and Windows
Arch Linux
NodeJS: 18.7.0
NPM: 8.17.0
Windows 10
NodeJS:17.17.3
NPM:8.12.2
What happened?
Press CTRL + SHIFT + P, select JavaScript Standar Style: Fix all auto-fixable Problems and an error pops up. 'undefined is not validating any files yet Source StandardJS - JavaScript Standard Style (Extension)
What did you expect to happen?
The extension to format the document
Are you willing to submit a pull request to fix this bug?
Never done that before, but I am willing to learn
I also reverted back to the vscode-standardjs (old version) by Sam Chen using ext install chenxsan.vscode-standardjs. This package works as intended on both systems (Linux and Windows). This only started happening after I migrated to the new supported version
The text was updated successfully, but these errors were encountered:
What version of this package are you using?
v2.1.0
What operating system, Node.js, and npm version?
I am getting the same errors on both Arch Linux and Windows
Arch Linux
NodeJS: 18.7.0
NPM: 8.17.0
Windows 10
NodeJS:17.17.3
NPM:8.12.2
What happened?
Press CTRL + SHIFT + P, select JavaScript Standar Style: Fix all auto-fixable Problems and an error pops up. 'undefined is not validating any files yet Source StandardJS - JavaScript Standard Style (Extension)
What did you expect to happen?
The extension to format the document
Are you willing to submit a pull request to fix this bug?
Never done that before, but I am willing to learn
I also reverted back to the vscode-standardjs (old version) by Sam Chen using ext install chenxsan.vscode-standardjs. This package works as intended on both systems (Linux and Windows). This only started happening after I migrated to the new supported version
The text was updated successfully, but these errors were encountered: