Can we publish this to Nuget instead of NPM?

[mabasic]

I was looking into writing a VS Code Extension using F# and have found myself going down the wrong rabbit hole.

fable-compiler/fable-vscode-extension#1 (comment)

I have tried using Fable.Import.VSCode but got some error regarding missing PromiseLike in Fable.Core or something like that. Then I realized that that package is very old (2017) and only then have I found this repository where you are using a version from ionide/ionide-vscode-helpers NPM package. ../node_modules/ionide-vscode-helpers/src/Fable.Import.VSCode.fs.

If I am a developing an extension using F# and I want to use a F# package I tend to look on nuget.org not npmjs.org. It seems very strange to install a NPM package just to have to reference it by path in .fsproj file. Also, there is no versioning as much as I can find...

Can we publish this to Nuget and provide a version?

The old code is here and it is published on Nuget:

https://github.com/fable-compiler/fable-import/tree/master/VSCode
https://www.nuget.org/packages/Fable.Import.VSCode#versions-body-tab

Can we decide which version will go forward and make one deprecated?

On a side not I can't even find this package on npmjs.org so I have no idea from where am I getting this package.

[baronfel]

I'm not up to date with what the current Fable packaging recommendations are, but would happily do whatever the recommendation is. I don't know anything about the age/provenance of the NPM.version, but it does seem that if it truly is that old it might be best to unlist it?

[MangelMaxime]

Using NPM is a relic from the past it was how things where done in Fable 0.X and 1.X.

Documentation on how to package a Fable package can be found here.