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
-
@devRancid
More like, it's not my job to deal with that.
It's not my issue. I'm told "exclude this and include this".
Sure, I know how TS works, but I'm not paid to care what the devs do with the gitignore, and not paid to care what idiosyncrasies they follow.
If you tell me "ignore what's in gitignore except for build artifacts", I'm gonna do just that.
And I could bet at least half of people reading this (and I'm being conservative) didn't actually know what I posted. -
In adding to that, most JS devs have no clue of all the shit their retarded ecosystem produces.
I don't care to learn it. If they tell me "ignore it cuz it's in gitignore", I do just that.
In any case, I don't really care, I'm a chunky less poorer thanks to it, so, please keep not knowing shit about your VCS. 😂
God, so tilted right now, after having to "urgently" (joke's on them, they will get charged the urgent rate) check why some deployments weren't working due to some npm dependencies not being found.
(Just from mentioning npm you surely think I'm gonna bash JS, but no!)
I'm tilted by TS devs that don't bother to learn the very basics of git pathspecs and just add "dist" to their .gitignore, not knowing that it's gonna exclude any file or directory named "dist" *ANYWHERE* in the project.
And when your poor CI pipeline tries to transfer the build artifacts (so, keeping the .gitignore excludes but manually including node_modules and dist), it excludes the dist dir in some packages and wrecks the deployment.
Please,, please, PLEASE.
if you want to:
A) Make your entry relative to the .gitignore...
Put a slash first.
B) make it only match directories and not files...
Put a slash last.
rant