I'm a Sr. Software Engineer at Flashpoint. I specialize in Python and Go, building functional, practical, and maintainable web systems leveraging Kubernetes and the cloud. Blog opinions are my own.
I'm never sure about what the "right" way is to setup for a small project. I'd like to use ES6 and modules, etc. but I've learned JS from so many different sources that it's hard to figure out what's out of date knowledge and what's current. I know that you can use a big build pipeline for larger projects, but I'd like to know what's recommended for a smaller project. It would be really nice to make a project, and know how to get some of those nice modern JS benefits without having a huge, scary node_modules folder.
I'm a Sr. Software Engineer at Flashpoint. I specialize in Python and Go, building functional, practical, and maintainable web systems leveraging Kubernetes and the cloud. Blog opinions are my own.
Yeah, the language features and syntax I get (although I love reading posts about them, don't get me wrong). Coming from other ecosystems (Python, Ruby...), getting a project set up and going to the point where I can actually start using the syntax theory that I know is what trips me up. I generally get started and confused and end up reverting to the ES5 that I know will work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm never sure about what the "right" way is to setup for a small project. I'd like to use ES6 and modules, etc. but I've learned JS from so many different sources that it's hard to figure out what's out of date knowledge and what's current. I know that you can use a big build pipeline for larger projects, but I'd like to know what's recommended for a smaller project. It would be really nice to make a project, and know how to get some of those nice modern JS benefits without having a huge, scary
node_modules
folder.So, you're more concerned about the ecosystem instead of programming JS?
Yeah, the language features and syntax I get (although I love reading posts about them, don't get me wrong). Coming from other ecosystems (Python, Ruby...), getting a project set up and going to the point where I can actually start using the syntax theory that I know is what trips me up. I generally get started and confused and end up reverting to the ES5 that I know will work.