ChakraCore NuGet: Follow-Up Items

[dilijev]

Follow-up from #85

Possible Work Items

• Include a change.json file in the NuGet packages to provide easily-accessible information about the commit the package was built from.
• Integrate with MyGet's SymbolSource infrastructure to enable debugging when needed without having to ship the debugging symbols with every binary package.
• Split NuGet feeds for entire set of dev files versus just what is needed for deployment. (REVIEW: Is this useful? Possibly for scenarios which require low disk usage and/or low-bandwidth for downloading packages. What does "just deployment" look like?)

Future Work (maybe split into a new issue)

• NuSpec for Linux and OS X Native Development
• NuSpec for Linux and OS X .NET Development
• MyGet feed for preview builds of Linux targeted binaries
• NuGet feed for official Linux and OS X builds

Related to releases but not NuGet:

• (See Make official ChakraCore binaries easily available to developers on *nix platforms. (e.g. deb and brew feeds) #2278): Make xplat binaries more easily available to xplat users.

/cc (interested ChakraCore maintainers) @digitalinfinity @boingoing @liminzhu
/cc (folks from #85) @ormico @matthargett @pre10der89 @resnyanskiy @gulbanana @jimmcslim @Oceanswave

[Oceanswave]

As it was desirable for me to have the ChakraCore libs on NuGet, I published some packages here:

Platform Independent (Targets Win-x64, no Arm builds)
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore/

Win-x86
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore.win-x86/

Win-x64
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore.win-x64/

Win-arm
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore.win-arm/

macOS-x64
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore.osx-x64/

linux-x64
https://www.nuget.org/packages/BaristaLabs.BaristaCore.ChakraCore.linux-x64/

Source/Scripts:
https://github.com/BaristaLabs/BaristaCore-ChakraCore

Builds are directly from the ChakraCore releases -- library naming aligns what a .Net Core app can pick up in a x-plat manner via a DllImport attribute with a minimum of hassle. YMMV.

[dilijev]

@Oceanswave we already have our releases on NuGet (though not Linux and OSX binaries since we did not initially see value in providing those binaries for platforms that generally do not use NuGet). https://github.com/Microsoft/ChakraCore/wiki/NuGet-Packages

Edit: I see the future work references Linux and OSX binaries. Thanks for taking the initiative on that. We're happy to try to improve our NuGet offerings.

@sethbrenith @MSLaguana we could use this as a starting point if we wanted to publish xplat binaries this way, assuming the infrastructure for NuGet publication can handle multiple platforms.

[jtaylor100]

I am currently building a product written in a windows environment and deployed to linux docker containers. Having the latest linux binaries distributed through Microsoft.ChakraCore would greatly simplify our build process.

[schmitch]

Actually for .net core OSX and Linux NuGet packages would be really helpful, think about production SSR where you only build a .net application and you can have SSR within .net core with chakra instead of installing nodejs.