Hacker Newsnew | past | comments | ask | show | jobs | submit | ludlu's commentslogin

For node projects I use ts-node with nodemon watching for filechanges and takes care of restarting the server. And then to build the project for release thats done with tsc.


I've been using tailwind for almost a year and I love it. I would not use something else willingly for something new! Its easy/fast to write and in my mind VERY readable, and if you don't know whats what, their docs are really good.

And for example in React to build a component with conditional styling I use classNames and use props that correspond to classes.

https://github.com/JedWatson/classnames


Check out something like pkg by zeit[0] which compiles the node app to a binary. Then put it in a directory in your $PATH and you'll be able to run it as `fibonacci`.

[0]https://github.com/zeit/pkg


The easiest way is simply to use npm's bin, which if installed globally (npm i -g my-command) is added to path.


I’m interested in making binaries, to hopefully ease distributing in-house utils. Our various projects depend on misc node versions and reinstalling our utils to each new global bin ain’t fun. If there’s a better way, I’m all ears.


Please don't use this if the project is for work/something you care about, because it's a bitch to support in production, especially when compatibility becomes an issue. Better to not mention it at all in a work related context and just say there's no way to distribute nodeJS applications as binaries.


Alot of swedes emigrated to the US around 1800-1900s and spread all over the country. https://en.wikipedia.org/wiki/Swedish_emigration_to_the_Unit...


Thanks. Tangentially, search for "The Alot is Better Than You at Everything"



Oh that makes "Alot of swedes" a terrifying concept.


That's exactly the case for my family! However, we lost our umlaut at Ellis Island.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: