Closed atsushieno closed 3 years ago
While exploring possibility on JS module migration to JS-IR and TypeScript support, I created a patch to make it, but the resulting code is annoying in that it requires ugly changes in the existing code. https://gist.github.com/atsushieno/07a05734024d711b00b49664d32750a6
TypeScript support is IR-only feature, which requires various annoyances. I would just go with JS Legacy with manual typings if I want.
mugene npm packages are published. One step forward.
vscode-extension now works, compiles MML to .mid or .umpx, and errors are reported on the diagnostics. Needs packaging work.
It is currently blocked by:
Executing prepublish script 'npm run vscode:prepublish'...
> vscode-language-mugene@0.2.15 vscode:prepublish
> tsc -p ./
❌ Command failed: npm list --production --parseable --depth=99999 --loglevel=error
npm ERR! code ELSPROBLEMS
npm ERR! missing: @js-joda/core@3.2.0, required by Kotlin-DateTime-library-kotlinx-datetime-js-legacy@0.2.1
npm ERR! A complete log of this run can be found in:
npm ERR! /home/atsushi/.npm/_logs/2021-08-12T12_56_15_607Z-debug.log
See the documentation for more information:
https://github.com/eclipse/openvsx/wiki/Publishing-Extensions
I shoot the question on how to resolve this issue at javascript channel on Kotlin Slack, but got no answer. I don't think there is anyone who used Kotlin/JS to publish VSCode Extension at the moment.
Fixed as 0d0e005.
We likely have to fix JS stream resolver issue and any relevant JS issues first. Once it's done, we can start importing "vscode-extension" into this repo. This time don't have to run .NET command anymore!