-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provide official NuGet versions packages #3940
Comments
+1 to this. It's a real need.Regarding the unofficial packages, one of them was updated to v1.5, but unfortunately it's missing locale files, which ends up in an unsuccessful build. |
I'm curious why you'd need a TypeScript package for ASP.NET? In AspNet current you can use VS's built in MSBuild support and in AspNet you can use the NPM/Gulp/Grunt supper. A NuGet package almost seems redundant. |
Well, when new developers join my development team, they only requirement is Visual Studio right now. |
I'm also interested in this for the reasons stated above, for us trying to reduce setup and to rely solely on visual studio being installed would be very helpful. |
Are you expecting NuGet to provide the msbuild support required for typescript? |
I published a couple of NuGet packages to [https://www.myget.org/users/typescriptteam](the new TypeScript page on MyGet.org). The following packages are published:
Although the version of the packages is 1.7-rc, the components are the 1.7 RTM components. I marked the packages as RC, since this is their first release and we're explicitly looking for feedback on them. In the future we plan to publish the RTM bits to NuGet and have nightly builds on MyGet.org. With that, let me know how we can make them better and more useful for you. You can access the packages in VS by adding a 'package source' in Tools > Options. |
Official stable packages are available here: And nightly packages here: |
Hi team,
Thanks a lot for providing an official NPM package. That certainly comes in handy when building web apps on a lot of platforms.
However a lot of projects are using TypeScript in conjunction with Asp.NET and those projects typically already use NuGet for package management. It would be easier for those projects to use a single system.
I realize that providing NuGet packages will result in more cost to maintain two sets of packages but it may be worth it; please prioritize accordingly.
There are two different unofficial packages out there but neither has updated to v1.5 yet and it would perhaps be better to have at least one core team member as a collaborator on those.
Thanks.
The text was updated successfully, but these errors were encountered: