Building a JavaScript Development Environment – Live on Pluralsight!

I just published my newest course on Pluralsight! Building a JavaScript application from scratch today is overwhelming. You have to make decisions about package management, bundling, linting, transpiling, automated testing, and more.

In fact, there are over 40 decisions to consider!

Creating a JS Dev Environment - 40 decisions

Building a JavaScript Development Environment“, provides a playbook of potential options that detail a clear path through the key decisions. Along the way, you’ll build a robust automated development environment from the ground up using ES6.

You’ll learn how to set up a reusable development environment that provides a powerful foundation for future projects. You’ll also get to see how to create this environment so that it’s tailored just for your team’s needs.

After completing this course, you’ll have built a robust, responsive automated development environment that handles package management, bundling, linting, transpiling, automated testing, and much more, all with a single command.

Stop starting from scratch. Build a JS Dev Environment!

Subscribe to Email Updates (No spam. Just new posts.)

12 thoughts on “Building a JavaScript Development Environment – Live on Pluralsight!

  1. Hello Cory,

    Your pluralsight course is solid as a rock! You did a very good job there. Exactly what I wanted to learn. You somehow read my mind 🙂 Highly recommended.

    Thank you a lot!
    Jon

  2. Hi Cory,
    I am almost half way through your course (bundling..) and It is a wonderful course, I am really liking it.
    My question is this ->
    you have given so many options and suggestions and each option can be a whole course in itself,(webPack)
    Should I jump back and forth between them(selected ones) in order to get the maximum out of your course or follow along as is.I am also a beginner in JavaScript but I am able to get what’s happening.

    Thanks,
    Manik

    • Hi Manik – You’re right, each option could be its own course. And many options indeed are! That said, I deliberately leaned toward the most popular options. The tricky thing is some choices preclude other choices. For example, if you choose TypeScript instead of Babel, there are certain other things like ESLint that you can’t currently use. And if you choose Browserify, then the production build module will obviously be very different.

      In summary, I’ve used most the options I discuss and strongly believe in the stack I ultimately selected. So if you’re new, I’d suggest just following along with my suggestions. Then, you can begin trying alternatives once you’re comfortable and have something that works.

  3. Hello Cory, I am learning Angular 2 and React at present, will this course be helpfull to me in the long run, as both Angular 2 and React need us to know JS but not an expert in JS, as you know a lot.

    Keep up the good work.

    Thanks,
    Christina

  4. Hi Cory,

    What an amazing course… Excellent material… but I’m stuck at the module to generate the fake data.

    What would be the best channel to ask the question and post the error message?

    Regards…

    Rodrigo

  5. Cory, this course is great. I’ve been doing web development for a long time but I still learned a lot from your course. It really helped me filter a lot of the noise and see some solid examples of how things actually work. I also appreciate you discussing the reasoning behind why you may chose a particular tool over another versus being a zealot to a particular tool or method. Please keep up the good work and giving back to the community!

  6. Would you recommend using typescript ? If your coming from the C# server side and wanting to start going onto client side?

    I’ve heard it does the job for prototyping, however from a pragmatic architectural perspective, I’d be able to write in Typescript quicker than if I learned a new framework or raw js.

    • TypeScript is certainly approachable for C# devs. That said, I’m a C# dev and prefer plain JS because with ES6 JS finally became mature enough that I don’t miss what TS offers. With a solid editor, transpiler, linter, propType declarations, and tests, I have all the “safety” I need. I enjoy JS’ dynamic nature. It feels like a better fit for the front-end to me. Personally, I prefer strong types on the server and dynamic types on the client, but to each his own. TS is a mature option that many enjoy so certainly worth trying yourself!