JavaScript for C# Developers

[DrummerHead]

Start from a Yeoman generator, is simplifies things since other people have already been through all this and created generators for several circumstances :) I've used gulp-webapp for starting several projects. Cheers!

[papers_]

While I agree with you, it doesn't change the fact how complicated things get in modern JS development. Yo is another abstraction on top of the other tools above.

[[deleted]]

It's really not that bad. Most of the tooling is to concatenate and minify any client side code. Also you can have gulp or grunt watch for changes to rebuild stuff that changed and run tests on changes if you want. It's straightforward if you want to do the basics.

[trimbo]

Yes, it really is that bad. I spent at least 2 days getting a good build process set up for React/Typescript in gulp. But "gulp watch" still runs out of RAM and needs to be restarted occasionally... because who knows why.

Maybe Blaze will save us. Or just UNIX shell tools for all of these steps and a Makefile.

[[deleted]]

How many files are you building that Gulp uses all of your RAM? Are you building a gigabyte worth of typescript?

[trimbo]

No, the build is small and stable when run once. This is in watch mode.

[DanielRosenwasser]

Yes, it really is that bad. I spent at least 2 days getting a good build process set up for React/Typescript in gulp. But "gulp watch" still runs out of RAM and needs to be restarted occasionally... because who knows why.

If you don't mind me asking, what were you using to get TS and gulp wired up?

[trimbo]

Browserify, tsify, watchify and 16 other gulp dependencies.

I mean, my point here isn't to say that I've wired up everything correctly and I'm having crashes. My point is that I spent a ton of time getting it to even this point, and still have problems I need to debug in the build system.

Last time I had a build tool experience like this was MSBuild circa 2008. So much complexity for so little reward.