Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "yeoman"
-
Slept at 3am working on a personal open source yeoman generator that will probably be used by left than 10 users. 😀😀2
-
Damn frontend crap.
The fact that you have to mask all of the disease with processable versions of css, html & js is bad enough, but there are like 6 dialects of each bandaid, and every project has traces of each.
The the design kid tells me to run this grunt script, frontender number two screams "no, dont use grunt, we use gulp! or was it bower? I guess just run it through yeoman, it's easy!", after which the third fucking shitty hipster yells "No that's outdated, just edit the webpack file, and then run yarn install... oh but run npm upgrade --global yarn first"
Did you just fucking tell me to upgrade a fucking package manager with another package manager?
Composer, gem or cargo are not always without problems. But at least us backenders have our fucking shit together. The worst we have to deal with is choosing Python 2 vs 3, or porting some old code so the server can migrate to PHP7.
The next person to tell me they found this awesome tool to manage his other tools... I'll fucking throw your latte all over your wacom tablet.2 -
When you install npm to install an older version of npm to install a yeoman and install a generator that generates a generator.2
-
NPM feels so broken, so scared to try some Yeoman generators cuz know ill waste 30m making it work..3
-
Just finished up my weekend side project. Checkout https://github.com/ndelvalle/... and let me know what you think.
-
What do people think of automated code generator frameworks such as Yeoman and Plop? Any experiences to share using those or similar frameworks?
I like the idea of automation, it means code will be consistent (especially across teams), and it means less boilerplate writing that potentially breaks thought processes.
But then does it just waste time? It's something extra to develop, test and debug. Further most of dev time is reading, thinking and modifying.2 -
Yeah, I have some friends, but none of them appreciates Yeoman like I do.
Fuck, they don't even know what it is. 😡😡😡1 -
This depends mainly on the programming language with which I want or have to develop a project.
I like to use Behat for PHP and other simple things. At the moment I only have clients who want to implement projects in PHP. God knows why.
For more complicated things I like to use yeoman, but I have to say that there are also a lot of horrible generators, so I follow the official instructions more often.
Otherwise, the usual procedure:
1) git init
2) Planning of features and functions (if not already specified by the client)
3) Select frameworks (mostly necessary)
4) Start programming
5) Commit often
6) Commit often
7) Commit often -
React, redux and electron. Why can't you be simple 😂.
Might consider writing a yeoman generator when I find something that works!1 -
Fucking Yeoman, guys.
For a school project I thought I'd try it out to scaffold out my folder structure etc. Ran a php generator (not having commits since 2013) through npm and sipped my coffee while one node deprecation warning after the other filled my terminal.
Now I just feel like I'm sitting with my dick in my hand while staring at what looks like the fucking source code of the Matrix itself.
Does anyone use Yeoman for PHP projects anymore?
Well, at least Grunt works flawlessly 😎 -
Lately been doing a lot of GitHub action stuff so created a Yeoman generator to scaffold javascript-based Github actions.
You can check the project here if you want 🦄
https://github.com/RocktimSaikia/...