Moving from Node.js to ASP.NET Core

Re:Moving from Node.js to ASP.NET Core by untog on Sunday April 02, 2017 @05:42PM (#14019187)

Just to throw out the obvious: it should be trivial to get some old Node code up and running, particularly if you don't mind using an old runtime version. If you've run npm shrinkwrap you have a log of the exact versions of each package used. You don't have to use ES6 or Typescript, you can keep on trucking the same as you ever did.

It sounds like the author was an ASP.NET developer, dabbled a little in Node, then worked with Xamarin (also .NET) then moved to ASP.NET Core. Nothing wrong with any of that, but it only stands to reason you'll find ASP.NET easier to work with than Node when you've used it extensively and Node not very much at all.

[ Parent | on HN ]

Re:Moving from Node.js to ASP.NET Core by CSMastermind on Sunday April 02, 2017 @07:11PM (#14019562)

As a node developer, I've learned the value of shrinkwrap the hard way. I imagine many companies don't use it until it comes back to bite them.

I've had to deal with downstream dependencies breaking things in our dev environments more than I care to admit. I'd suspect that most old node projects of any meaningful size won't just boot up and run without some tinkering.

[ Parent | on HN ]

Re:Moving from Node.js to ASP.NET Core by vmasto on Sunday April 02, 2017 @07:58PM (#14019765)

Thankfully Yarn is here to solve most (if not all) of these problems.

[ Parent | on HN ]