Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "gulp"
- Sure! What do you need?
Oh, it’s very simple, I just want to make a static webpage that shows a clock with the real time.
- Wait, why static? Why not dynamic?
I don’t know, I guess it’ll be easier.
- Well, maybe, but that’s boring, and if that’s boring you are not going to put in time, and if you’re not going to put in time, it’s going to be harder; so it’s better to start with something harder in order to make it easier.
You know that doesn’t make sense right?
Okay, so I want to parse this date first to make the clock be universal for all the regions.
- You’re not going to do that by yourself right? You know what they say, don’t repeat yourself!
But it’s just two lines.
- Don’t reinvent the wheel!
- One component per file!
- It happens, and you’ll get lost managing your files as well. You should use Webpack or Browserify for managing your modules.
- Yes, but some people still have previous versions of ECMAScript, so it wouldn’t be compatible.
Why is it called ECMAScript then?
- It’s called both ways. Anyways, after you install Webpack to manage your modules, you still need a module and dependency manager, such as bower, or node package manager or yarn.
What does that have to do with my page?
- So you can install AngularJS.
Oh, that’s great, so if I modify one sentence on a part of the page, it will automatically refresh the other part of the page which is related to the first one and viceversa?
- Exactly! Except two way data binding is not recommended, since you don’t want child components to edit the parent components of your app.
Then why make two way data binding in the first place?
- It’s backed up by Google. You just don’t get it do you?
I have installed AngularJS now, but it seems I have to redefine something called a... directive?
- AngularJS is old now, you should start using Angular, aka Angular 2.
But it’s the same name... wtf! Only 3 minutes have passed since we started talking, how are they in Angular 2 already?
- You mean 3.
Okay, I now know Angular 6.0, and use a component based architecture using only a one way data binding, I have read and started using the Design Patterns already described to solve my problem without reinventing the wheel using libraries such as lodash and D3 for a world map visualization of my clock as well as moment to parse the dates correctly. I also used ECMAScript 6 with Babel to secure backwards compatibility.
- That’s good.
- But did you use TypeScript?37
2010: PHP, CSS, Vanilla JS, and a LAMP Server.
Ah, the simple life.
2016: Node.js, React, Vue, Angular, AngularJS, Polymer, Sass, Less, Gulp, Bower, Grunt.
I can't handle this, I'm shifting domains to Machine Learning.
2017: Numpy, Scipy, TensorFlow, Theano, Keras, Torch, CNNs, RNNs, GANs and LOTS AND LOTS OF MATH!
Okay, okay. Calm down there fella.
This was over a year ago now, but my first PR at my current job was +6,249/-1,545,334 loc. Here is how that happened... When I joined the company and saw the code I was supposed to work on I kind of freaked out. The project was set up in the most ass-backward way with some sort of bootstrap boilerplate sample app thing with its own build process inside a subfolder of the main angular project. The angular app used all the CSS, fonts, icons, etc. from the boilerplate app and referenced the assets directly. If you needed to make changes to the CSS, fonts, icons, etc you would need to cd into the boilerplate app directory, make the changes, run a Gulp build that compiled things there, then cd back to the main directory and run Grunt build (thats right, both grunt and gulp) that then built the angular app and referenced the compiled assets inside the boilerplate directory. One simple CSS change would take 2 minutes to test at minimum.
I told them I needed at least a week to overhaul the app before I felt like I could do any real work. Here were the horrors I found along the way.
- All compiled (unminified) assets (both CSS and JS) were committed to git, including vendor code such as jQuery and Bootstrap.
- All bower components were committed to git (ALL their source code, documentation, etc, not just the one dist/minified JS file we referenced).
- The Grunt build was set up by someone who had no idea what they were doing. Every SINGLE file or dependency that needed to be copied to the build folder was listed one by one in a HUGE config.json file instead of using pattern matching like `assets/images/*`.
- All the example code from the boilerplate and multiple jQuery spaghetti sample apps from the boilerplate were committed to git, as well as ALL the documentation too. There was literally a `git clone` of the boilerplate repo inside a folder in the app.
- There were two separate copies of Bootstrap 3 being compiled from source. One inside the boilerplate folder and one at the angular app level. They were both included on the page, so literally every single CSS rule was overridden by the second copy of bootstrap. Oh, and because bootstrap source was included and commited and built from source, the actual bootstrap source files had been edited by developers to change styles (instead of overriding them) so there was no replacing it with an OOTB minified version.
- It is an angular app but there were multiple jQuery libraries included and relied upon and used for actual in-app functionality behavior. And, beyond that, even though angular includes many native ways to do XHR requests (using $resource or $http), there were numerous places in the app where there were `XMLHttpRequest`s intermixed with angular code.
- There was no live reloading for local development, meaning if I wanted to make one CSS change I had to stop my server, run a build, start again (about 2 minutes total). They seemed to think this was fine.
- All this monstrosity was handled by a single massive Gruntfile that was over 2000loc. When all my hacking and slashing was done, I reduced this to ~140loc.
- There were developer's (I use that term loosely) *PERSONAL AWS ACCESS KEYS* hardcoded into the source code (remember, this is a web end app, so this was in every user's browser) in order to do file uploads. Of course when I checked in AWS, those keys had full admin access to absolutely everything in AWS.
- There was no error handling or reporting. An API error would just result in nothing happening on the front end, so the user would usually just click and click again, re-triggering the same error. There was also no error reporting software installed (NewRelic, Rollbar, etc) so we had no idea when our users encountered errors on the front end. The previous developers would literally guide users who were experiencing issues through opening their console in dev tools and have them screenshot the error and send it to them.
- I could go on and on...
This is why you hire a real front-end engineer to build your web app instead of the cheapest contractors you can find from Ukraine.19
I just hate npm dependencies.
If you want to write a small website with npm dependencies (some frontend deps like Bootstrap and some development deps like gulp or babel) you will have more npm dependencies in your project than own code. It is ridiculous, how some lazy developers just add dependencies to their projects, without evaluating their dependencies. The source code of one of my projects is around 4MB (without any dependencies). If you then run yarn as required, it grows to around 80MB (where 73MB are node_modules).
This is just terrible.
I rant about this, as I made the mistake to upload my node_modules directories when restoring a backup of my server. Worst idea one could ever have.9
npm install && gulp
...9 years later...14
It's Friday, and I'm working from home. What better way to start the day with gulp and coffee with icing on donuts... Happy Friday to all :)16
When you build a beautiful set of Sass files with grunt/gulp tasks, hand it off to another developer who makes all their changes in the compiled css.3
The intern has directly editted the CSS file then push to the repo.
The senior optimized the old codebase and compiled the SCSS with gulp leading to the CSS file rebuild.
The vicious cycle continued until code review which was like 2 weeks later.3
Note: our PM is new.
PM: can you help me?
Me: sure, what do you need?
PM: where do the folders with all the techie stuff come from?
I had no context and spent the next 20 minutes trying to work out what folders she was on about. Turned out she wanted to know where the client side folders on our development server come from, was going to explain 'Gulp' and 'Branch' to her but I think I'd be there for the rest of the day... Why do 'tech' companies hire non-tech-savie people.4
So I spent 4-5 weeks explaining how shit the current code base was, implemented gulp tasks to lint js, CSS etc, written shed loads of coding standards and best practices to follow. At this point everyone was onboard with the changes and thought brilliant were going to start getting some good code coming out of this team.
I go on holiday for a week, come back and fucker has ignored the documentation disabled the linters in the gulp tasks and the code is back to square one SHIT!!
Plus everyone still committing to master!!!!
Why do I bother!!7
I recently joined this big MNC after shutting down my own startup. I was trying to automate their build process properly. They were currently using grunt and I favor gulp, so I offered to replace the build process with gulp and manage it properly.
I was almost done with it in development environment and QA was being done for production.
In the meantime I was trying to fix some random bug in a chrome extension backend. I pushed some minor changes to production which was not going to affect the main site. That was in the afternoon.
This Friday my senior rushed to me. It was like he ran six floors to reach me. He asked, did you push the new build system to production, I refused. He then went to the computer nearby and opened the code.
It was Friday and I was about to leave. But being a good developer, I asked what's the problem. He told me that one complete module is down and the developers responsible for them left for the day already and are unreachable.
I worked on that module multiple times last month, so I offered my help. He agreed and we get to work.
The problem was in the Angular front end. So we immediately knew that the build process is screwed. I accidentally kept the gulp process open for anyone, so I immediately rebuilt using grunt and deployed again, but to no success.
Then I carefully analyzed all the commits to the module to find out that I was the one who pushed the change last. That was the chrome extention. I quickly reverted the changes and deployed and the module was live again. The senior asked, how did you do that? I told the truth.
He was surprised that how come that change affect the complete site too. We identified it after an hour. It was the grunt task which includes all the files from that particular module, including chrome extension in the build process.
He mailed the QA team to put Gulp in increased priority and approved the more structural changes, including more scrutiny before deployment and backup builds.
The module was down for more than 5 hours and we got to know only after the client used it for their own process. I was supposed to be fired for this. But instead everyone appreciated my efforts to fix things.
I guess I am in a good company 😉4
Feeling like I've gone back in time about 15 years!
Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.
His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".8
And what really crawls my balls is that I can write Sass and Jade, even use partials and organized the shit out of this website, and let Gulp just vomit some minified HTML and CSS on the other end.
Man that feels so good.20
Share your VS Code installed extensions here.
Mine is: Alignment, Better Comments, change-case, Colonize, CSS Peek, DotENV, File Utils, GitLens (my favorite!), Gulp Snippets, JS-CSS-HTML Formatter, Laravel 5 Snippets, Laravel Blade Snippets, Material Icon Theme, npm Intellisense, Numbered Bookmarks, Path Intellisense, PHP Debug, PHP DocBlocker, PHP Intelephense, PHP IntelliSense, Prettify JSON, Quokka.js, snippet-creator, Vetur.
Feels like there are redundant extensions here that I need to uninstall.
Happy Friday and Cheers! Excited for Infinity War movie! 😎18
this is getting ridiculous8
Just got given my own internal project at the company I work for! Basically I created a gulp task for one of our projects that allows us to use version control with Salesforce in a pretty easy way and deploy without a stupid IDE (like eclipse) getting in the way. Now they want me to turn that idea into a node module we can use company wide!5
I recently moved all our tasks from grunt to gulp and integrated bower as the front end package manager. Also I wrote a lot of guides to set up standards and how-to for the team.
It's my 3rd month in my job and first major work. It took me more than a month to completely set it up and train everyone to use those new integrations.
Today all my seniors applauded my efforts. So much happiness 😀3
A fairly simple and basic single page-ish project with no framework at all.
No backend or database.
Plain old Gulp task, npm scripts and Webpack.
Some parallax and other scrolling effects.
Client is actually a pretty simple, cool and understanding guy.
This is too easy.
What is this madness??4
Me when I read about another JS framework, gulp module or workaround for using ES2016 features today.3
I'm surprised how after using gulp task with minify js, css, html, smoosh and compress to gz file the whole web size down from 200kb to 20kb.
That let me think what a shit web developer I'm and what cool are those things.1
Earlier this day, I was about to start a new project. So I copied my favourite gulpfile.js into that projects root and installed all dependencies with npm. After running Gulp for the first time it threw an error.
Silly me tried to fix stuff and got googling the error and trying random things... After a break of a few hours I just fucking rerun Gulp and read the fucking error completely. It stood there. The fucking solution just stood there, run "npm blah --force" to reconfigure package blah....
Of course it worked right away and I finally could start working. But this shit took way too long. Why I just can't read the fucking error message. Damn1
Getting ready for my new React project.
Vim: Check ☑
TernJS: Check ☑
Webpack: Check ☑
Gulp: Check ☑
Nodemon: Check ☑
Now I begin 😆7
Sick and fucking tired of this bullshit.
Previously worked with Laravel, used 'gulp watch' to watch for changes in assets and now they changed things for the better of Laravel Mix as a fucking wrapper for webpack. Now I have to do shit load more stuff to get gulp working, 'cause otherwise my 'npm run watch' shits itself every fucking time I run that shit, doesn't matter what fix is aplied. Battling that bullshit for 3 days now and shit's not working anyhow. Stupid fucking bullshit. Sorry, had to let it out from myself.9
Before I realized what a Vagrant Box was, I thought everyone was talking about cardboard boxes for homeless people.
So there I am thinking everyone was talking about homeless people and I finally understand that it's a service for quickly deploying VMs for local development when I get invited to a party after a convention with my hosting company and I look over the rail and see a vagrant man asleep on a cardboard box.
For the ultimate fuckit alias:
alias fuckit='git commit -am "$(curl -s whatthecommit.com/index.txt)"'
gulp && git add . && fuckit && git push && firebase deploy3
Was wondering why my script wasn't working. Added it to my node modules. Imported the style sheet with a require. Checked the gulp config file. Made sure it was in my pipeline. Checked my webpack settings and made sure jquery was loaded first. Checked my version on npm, crossed referenced with my package.json file. Why isn't it working....forgot to add the script tag in my html😤2
Do I do it?
*Heart rate intensifies*
I'm not used to spending big amounts of money
ps. Sorry for the bad image, was on a work pc27
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
Employer made me delete a CI script that checked if our Gulp compiled because a colleague convinced him that “if you upload broken code to git you shouldn’t be uploading it” ..do you even know what CI is for? Don’t you know that people will inevitably fuck up eventually? I want to rip my fucking hair out right now.
Been hacking frontend for a while, know most of the perks and tricks of css and html, have implemented countless of projects with angularjs, have even created jquery plugins and gulp packages, have won hackatons in UX design.... Still, a SFO company turned me down for a front end dev position cause I could not find the K most frequent words in an array in O(n) time complexity...3
I started working for myself in January, and work has been few and far between.
I’ve always wanted to work for myself, and now I’m working on a product I’m actually going to sell *gulp*
It’s not ready yet, but I’ll definitely be posting here about it when it’s ready to go :D
It’s going to be a super simple (Windows to start) screenshotting tool (and relevant cloud services) primarily focussed on devs / IT professionals and their needs.
Sound off for feature requests 👍4
Fuuuuuuuuuuccccccckk you gulp, you have one fucking job. Front-end web Devs this is a warning for all of you out there. Go with webpack always.5
Why aren't my js and CSS changes showing?!?!?!?!!!!??!!
F5, ctrl + F5, F5 and repeat
Oh yeah, gulp watch...1
Pls share your wisdom. Bye.5
Spent like 5 hours today installing, configuring, and playing with phpstorm. first time I've used a real ide type program and wow, I replaced 5 programs with this I would use at the same time.
filezilla (ftp), rapidphp (code), mysql workbench, cmd prompt (node, gulp, sass), and source tree (git)6
That'd be last year, on my first job as a registered employee.
After working years as a freelancer, and without a degree related to IT (I'm an advertising professional), kinda applied to the job and my application was accepted!
When I saw this, I had to spend the night learning how to use gulp, bower and AngularJS, since my JS experience was really small.
I did pass the test, he really recognized the effort, told me I did everything and even a bit more than requested and I was one of the two applicants that would be hired.
I really felt pround when I was told "we really like how your GitHub is mostly documented and well maintained, most applicants don't even care about it, some don't have a GitHub account".
After I got in, besides doing my AngularJS tasks, I did get mentored on how to code and think better, handling and developing APIs, better using Git and he also helped me get rid of all my doubts and fears about using Node.
Also, everyone on the IT dept. helped me get better with bits and pieces, and it really felt like the whole team kinda mentored me in some way.
Even though the job only lasted for 4 months, due to new CEO changing things, we still keep in touch and the CTO called me to do a really nice freelance job together.
Thanks to this job and his help, my React and JS skills really went up, and I could accept better jobs once I returned to the freelance route. :D
Sometimes I still have go down the PHP route (welp, money :/), but I'm forever thankful to the experience. :D
I don't know how those guy know angular 2 and react.js and know 3 different kind of build tool - grunt, gulp and webpack 2 in the same time. I'm struggle to understand redux. Many young genius coder lowered my self-esteem.3
Building a new machine for NodeJS. Installing Gulp-sass has a dependency on node-sass - which has a dependency on node-gyp - which has a dependency ON PYTHON!!!
and.... python 2.7, as it doesn't support 3.0
Doomed - We're all doomed.5
I have officially decided to use CI (Jenkins) at work because "apt-get update && apt-get upgrade -y && composer self-update && composer update && npm update -g && npm update && bower install --allow-root && gulp" after a pull doesn't seem healthy 😂2
If I had some reliable metric to measure bullshit per file, let's call it BPF, I believe the number would be highest on average for files named "gulpfile.js"1
I'm starting to use gulpjs and there is one thing that keeps me busy aside from looking for best dependencies for my workflow;
My current structure is simple af but somehow it works for me, but I'm still curious how to properly use assets, lib and vendor directories.
Been interested in trying Polymer for a while so gave it a try today, two hours later now and about to dropkick my laptop!
Followed the "this-looks-super-easy-guide" but that kinda turned into shit when it was time to run gulp!
How the f#*k can it be so hard to find information and get this to work!
Guess I'll just stick with my Android development and forget about this side project because it affects my mood in a bad f#*king way👹5
Just needed a good looking material os datepicker - ended up wrestling with react, webpack, npm and gulp. 3 hours later, ta-da, I have a datepicker! webdesign nowadays...
when the setup of programming environment takes more effort than the code.
and you're like fuck it i'll do it online!7
Fuck ES/TS 😐
Been trying for hours now to get ionic 2 to work with either generators or async functions. Doesn't work because async for ES 5 is only supported with TS 2.1 which breaks the angular compiler. Also can't use generators (not supported for es5 at all by TS).
Also can't really change the ionic build process to just take es6 output instead of es5 and transpile because it's a convoluted mess in a separate node module instead of just a gulp file like with ionic 1.x.
Why is the JS ecosystem such a fucking mess?3
-$ gulp test
*30 seconds later*
[oh wait, for got something... Typety type... Fixed. I don't need to rerun gulp test, right?]
-$ git push
*email from CircleCI: BUILD FAILED*
I hate it when people name fancy new techniques but don't actually know what it is. Today I had the following conversation with some of my ClassMates:
Me: Whe should bundle the js and css files of our app
CM1: I used Gulp before, maybe we could use that
CM2: I used Grunt in the past, but thats kinda old-school webpack is what everybody uses now
CM3: I heard Docker is also a great tool for doing webstuff, let's use Docker3
Webpack? More like Fudgepack 😡
I currently use Github as my git server and have worked a little bit with Travis. Sadly Travis can't deploy to local network targets and that's why I had the idea to create my own basic CI for the local network: It will be a simple nodejs-app and listens to pushes via Github Webhooks. Then it fetches the code from Github and runs a task runner like Gulp over it and tests it with any nodejs testing framework. Then it deploys the compiled, tested and linted app to the local network. What do you think of this idea?8
So CRA(create-react-app) v2 rolled out.
> started new project with my own boilerplate
> little did I know, I am accidentally doing int CRA2
> gulp-sass fails.
> Internal screaming.
> Bulma React Components fails to compile due to one type, IDK how they missed in previous build.
> fixed by removind browserlist array from package.json
> Guess what, it comes back as you close it.
> So, now I've to keep it open while gulp-sass is running, which is almost always, in order to compile.
Thank you and Fuck you facebook5
I promised to blow off unit tests, so here we go. Let’s talk about unit tests.
Why use them? So, unit testing connoisseurs outline two big purposes:
1. To keep application integrity,
2. To catch bugs.
Keeping app integrity is when your freshly hired developer implement something that potentially leads to the whole app failure, but unit test fails and tell you that newly added code is breaking the app.
Catching bugs is pretty much self explanatory. Just think about it – you have to actually write code that describes how to check up another code to catch bugs in it.
I personally hate unit tests. I can’t explain, but every time I forced myself to write them, I got vertigo and terrible headache to the end of the day. Trying to write some tests? Here you go, wooosh and you can’t work anymore. Go get some sleep if you can.
But I still needed my job to be done and it should have been done really well. So I started my research.
Recalling Steve McConnell’s and many other classy developers’ experience, there is only one decent solution that prevents bugs and inconsistencies at large scale – the specs. Developing the specs should be considered the task number one. With decent, robust specs, app is almost guaranteed to contain no bugs.
Let’s take a look at the piece of great spec. For example, imagine you have to implement validation logic. So you state that validation should be implemented with special validation functions and then you define what validation function is: a pure function that accepts a value and returns boolean: true if value is good, false otherwise.
With that in mind, it’s obvious that potentially present bugs can only be inside that pure functions. Our spec made implementing validation very easy and idiomatic, isolating potential bugs. As soon as validators are pure and simple, unit tests aren’t needed at all.
You know what? As your app scales, you’ll definitely need a spec, sooner or later. Growing up without spec leads to irreversible failure, your app will grow like cancerous cell does and it’ll be easier to just put it into trash and start up from scratch.
But specs have one major downside – it requires at least one enlightened developer with really great experience to create it. It can’t be done quickly, it’s a very costly and difficult process. That’s why making great software costs that much.
But what if you need an MVP right now?
Speaking of MVPs, you’ll have to go with simplest instruments possible. Throw away Jenkins, use your Plesk autodeploy from Git repo. Throw away complex frontend setups, go with $30-$40 glittery ui kit or even an open source thing right from CDN, without less, sass, gulp and all that jazz. Make use of create-react-app if you can’t avoid using React because you’re making a web application.
Throw away AWS, Azure, Docker, Kubernetes and everything like that. Buy a cheap PHP7 hosting with pre-installed MySQL and do everything as simple as possible. If you have to use NoSQL, go with free Heroku with git autodeploy, NodeJS Express and free Mongo addon.
MVP should be ready in two weeks. As soon as your infrastructure is that simple, you don’t need unit tests. They’ll slow you down. Once you MVP is ready, go get funding, throw away first MVP, hire a decent CTO and let him create the spec.
Right there, it may be noticeable that unit tests are probably the biggest and baddest workaround imaginable. It gives you false sense of controlling your bugs, while you don’t have any control at all. Obvious bugs that unit tests can catch are easily noticeable at concise system, while quirky bugs couldn’t be caught by them because you can’t even imagine them while writing your unit tests. At this point, unit tests are just waste of time.
So, the whole picture is clear: at a small scale, you don’t have time to write unit tests and don’t have many bugs because of simple tools and standard patterns. At large scale, you need a spec to prevent bugs, unit tests become redundant as long as your spec is good.
In conclusion, I can tell that I’ve been developing a Clojurescript + CouchDB app for some startup, and in 8 month coding by spec I made myself I encountered only two or three bugs, all related to external JS tools and its quirks.
Have a good time!7
I’m on a laravel project which is going great, the ass rapping part of it is compiling this fucking sass with laravel fucking mix... fuck it I’m setting up gulp4
const gulp = require("gulp"),
sass = require("gulp-sass");
const gulp = require("gulp"),
const sass = require("gulp-sass");
I use A17
Had an idea for a Webb app tonight that I could use to test some new things out. Didn't get round to the new things but 3 hours later I do have my IDE set up, quarter of a billion npm modules and a gulp flow so complicated it feels like the file system is a rubicks cube...
Received my first recruitment message on LinkedIn today. Generic as fuck "hey your profile looks nice, we have dis thing for you, come take a looksie".
Went ahead and read the whole thing, started laughing while reading requirements:
- own a degree in CS or related field: re-starting college next week
- extensive experience with automation processes: uuuh... I can write bash scripts and gulp tasks, how's that?
- extensive experience with Java, Angular, Selenium and Protractor: sure. Spent two weeks tinkering with those tools. Pretty much an expert already
- two years of experience: not even 6 months into my first job
And some other nonsense
Job would be in a very nice city, extended family lives nearby, actually a nice position. Too bad I am not looking for a job and my classes start on Monday 😂
But hey, at least people are looking at my profile! Yay!3
For the last time, ES5 DOESN'T support optional function parameters. gulp --production fails when running on testing when you do that.
*fixes gulp tasks to do gulp --production by default*
Next day : hey, why does gulp keep failing.
IT IS BECAUSE YOU DIDN'T LISTEN TO ME THE LAST 100 TIMES WHEN I SAID OPTIONAL PARAMETERS DOESN'T WORK WHEN MINIFYING
Let's see how you do it now.4
Is there somewhere an overview article/guide on the most popular software associated with web development? There are just so many technologies I know nothing about - Gulp, Grunt, Docker, Webpack, Bower and who knows what else..
Everyone seems to be using something else and it's just total chaos for me.2
me:task assigned is a small fix.Gonna finish Early sit back relax this sprint.
mail(next day):we've moved to microservices.setup as easy as gulp landscape:start
me:cool!shinny new stuff!seems easy!!
project:npm failed..please check module xxx..
after long mail chain
project:npm failed unknown file not found
after hours of googling and little github issue browsing
project:server running @ portxxx
me:yay finally happy life!!makes chnages, sent for review.
reviewer:code needs refactoring!!
me:make all changes..waits for faceless reviewer from another timezone!
me:i will make it in time!!!yes!!
me:no still i wont give up...
debug finds out new bugs caused by unrelated code...make new PR the end is near,one day more will definitely merge!!!
mail:jenkins down for maintenance!
me:nooooo....waits till last minute gets thumbs up for merge, finally merged in the last second!!
all for 12 lines of code change.
My colleague is having fever with reactjs and tools. Why the hell a 5 pages static cooperate website of our own need to use webpack?! How often we need to update the site? And today he spent whole day configure his gulp and deployment automation. If I were him, I would have finish the task with bootstrap, jquery and filezilla.3
I've just started freelancing on PeoplePerHour. I'm in talks to secure a job migrating a C# webapp to a desktop scenario using HTML5 embedded within WPF, but I've never done this as a solo project before. What sort of price is sensible to charge for this? I'm working in GBP1
Going back to a php project after writing loads of typescript on a node stack, I suddenly miss the instantanious feedback loop on file save via `nodemon` for basic scripts and `mocha --watch --reporter min` for tests.
Using phpunit, I currently have to rerun the test manually whenever I feel like. Which now feels so annoying. Cause I didn't know besser.
Now I was searching for something similar in php and I find answers pointing me to use either set up some npm hooks or set up gulp task or to use pywatch. phpstorm also is supposed to support file watchers and run test on every save, yet setting them up feels clunky.
Just read a rant about webpack and suddenly the hate boiled up again ...
Why is it just so damn annoying to configure?
Just make it like gulp or so where you have an actual idea on the workflow, rather than just throwing in plugins at random and let magic happen without knowing wtf is going on.
Tried to update an ejected Angular4 project to angular 5 ... after 2h i gave up and dropped some stuff to use angular-cli again.3
Lodash, Rimraf, Grunt, Gulp... I'm still not convinced that our frontend guy isn't just playing Pokémon Go all day3
When gulp takes 30 seconds to build... And you have to re-serve on every change.
Ready for webpack.3
When gulp build (expressjs + browsersync + browserify + uglify + gzip + gulp-zip + gulp-tar) perfectly compiles your code, minify and concat all js, gzipped them, minify images, package the files into a .zip and .tar... and refresh your browser 😍
you begin to have faith that its gona be a nice day ahead
Damn I'm tired of js build tools. Having just converted my build scripts to make is really making my day. Damn it's fast.
Account manager: could you amend these small, super tiny thing on *.*. Should only take you five mins.
Me: oh, the gulpfile is broken...
Me (5:30pm): oh, the gulpfile is broken...
Stumbled across a gist showing how to pass cli arguments to gulp tasks, suddenly found myself resisting the urge to cover every single line of the gulpfile in switches and arguments
Trying to create my own gulp build process since two days now...😖 Want to get the right folder structure and perfect build process on the first try, but that is exactly what is hindering me and I can't get any shit done...😟
Since I started my routine of checking bug logs every morning, I've had 2 instances where a website vulnerability scanner was run against a production website and generated over 2,000 Coldfusion errors.
At the time, I was super nervous about the apparent hack attempt, and hyped that the attackers never actually got in. It's nice to know that despite the various errors indicating vulnerable / breakable code, they were ultimately unsuccessful. I know now that a determined attacker could probably have wrecked our production websites. Since then I've made a ton of security-related updates and I'm actually thankful for the script kiddie getting my attention with that scan.
PS. We're now building a website for a local security company who is going to work with us to pen test the site when it's finished! Gulp.4
That moment when gulp run is as long as one epoch when training my neural network. How did we arrive here?
Spent 1 hour figuring out why an Exported Class ( Node.js) wasn't being picked up in a require statement by gulp. I have 2 clone software the same repo on my laptop. I put the new class on 1 repo and was running the gulp tasks from the other repo. Sigh.2
Question for you web devs out there.
I'm curious as to what your workflow involves for building and multi device testing? Whether it be grunt/gulp / something else?25
I'm looking for workflow/development environment ideas. Text Editor, CLI, GitHub... yarn... gulp... you get the point. Post your setups below! Screenshots would be lovely!2
I've just changed our style sheet generator to using gulp.
Took me 10 minutes to learn what to do (just css preprocessing with prefixes).
Grunt was horrid. We had it because the last guy thought "something new, I'll use this now", and it's never changed because no one understands it. Even after a few hours research.
Just closed VSCode running gulp, expecting it would terminate the session as well... it didn't.
Now I have no freaking idea how to shut the PowerShell running that shit.2
tl;dr: What's the best tuto/course for learning webpack ?
I'm mostly a PHP dev, working on my own framework, but I also use more and more JS, and recently some Typescript (and loved it).
But my usual gulp workflow starts to grow old and limited. ES6 modules seems a great improvement while every webpack user seems to say it gives headaches. So what's the best way to start ? ^^4
I'm in middle of fucking moronic, most incomprehensible situation.
So primarily I work for a project which requires Node 6.11.5 precisely and now I've been assigned another developer's half asses'd work without any documentation about how to set up gulp, long story it took me a week to figure out it's an ant build with node dependencies oh and I nearly forgot this developer is using node 0.12.1, Can you fucking believe that?
Now when I'll need to compile/build for primary project i'll need to reinstall 6.11.5 and god knows what will happen when and if that half asses'd project comes back
This idiot has style.css / style.ie.css / style.min.css in .gitignore so every time I pull I'll need to re-build oh and the worst part I spend my weekend fixing this shit then sass compiled and shit is still crazy, CSS is written from SASS but not reflecting on server ¯\_(ツ)_/¯
While I'm writing this I'm waiting on my boss who is also trying to fix this.
Just set up gulp for the first time... Now I'm just making stupid changes to see everything compile and reload the browser. What an Easter treat :D1
gulp started throwing premature close on useref:dist yesterday
said it was on a dependency
spent whole afternoon checking gulp issues and reviewing dependencies
as it turns out, it was nothing even remotely related to the error message
it was a spread operator used to merge objects
why must the Lord test me like that
Ain no missing semicolon like one in postcss w/gulp. HOW HARD IS IT TO SPECIFY WHERE THE UNEXPECTED SPACE IS?2
So I made a gulpfile.js boilerplate for starters with minimum node_modules as possible, I'd like if someone reviews my work : here's the link
started working on an existing project of a customer from our company today.
The readme.md says you need to run it in docker but apparently thats wrong. You have to symlink the repo inside wp-content/themes. Then install some packages via npm but only for node-7 because node-sass will only work that way. Then install some packages via bower becausy, why not? and lastly run a webserver via gulp that serves the parent wordpress-directory.
But wait, theres more:
The staging environment is a macbook for internals, thats running in our office 24/7 and serves the website via ngrok...
I really love this boilerplate for starting an Angular, gulp, browserify web app. https://github.com/jakemmarsh/...
When the projects repository has node_modules/, and you need build styles:
rm -rf node_modules/*
rm -rf node_modules/*
git checkout node_module/3
Jeej first project. Read: 101 FE bugs to fix. In code i've never seen before. With bare minimum support. Though day. First steps with Gulp are set. yay1
gulp.pipe(notify("SASS compiled, motherfucker!"));
I hate working on tight deadlines when I have plans the entire week, so I add some random shit to my gulpfile once in a while to cheer myself up.. Did not work, but I'm not gonna remove it.1
I resigned in last month. I worked as PHP dev and mostly in Laravel. I have little bit experience in angularJs. I want spend some time to learn new language and tech before I join in other company.
I want learn Go, Ruby and Python. Not all at once. I will mess around Aruidino a little bit as hobby.
I need your advice. As a PHP dev, Which language is easy to pick up? I mean PHP to other language listed above. I am not asking which is better than other. And will it be relevant to learn grunt, bower, gulp techs for a backend developer? And any other things you might want to suggests? I am open to suggestion.
Thank you in advance.
PS: Sorry for bad my English.1
Ugh! I'm trying to build a gulp-based workflow for WordPress theme development and it just isn't working (or flowing).
I'm debating whether to clear my gulpfile.js altogether and start again or attempt to build an npm-based workflow along these lines: https://keithcirkel.co.uk/how-to-us...3
> Gulp Task: https://pastebin.com/1d8k8juX
People! Do you know if there is something similar to gulp and modules like minify, uglify, smooth, etc (for HTML, CSS and JS) that runs in Python instead of nodejs? I can't install nodejs/npm in my job because "open source software is dangerous" :)15
Hi! I'm from Argentina, and on top of that from a relatively small city. Suffice it to say that there are next to none technology/programming/development events around. Do any of you know of a website where I can buy "stickers" ? I've seen some laptops full of grunt, gulp, GitHub, js, Python, etc etc stickers on top, and I wold really love to have some. Shipment is not an issue (as long as it ships within USA :P)
Thanks a lot !!!!2
Sophomore year starting soon so I'm looking for new project (s) to complete in parallel with the studies.
Some are more design-y and some more backend-y but I recently started getting better at designing so :)
1) Learn some fragment shader stuff. I've always been messing around with graphics and have a game on steam, so I think that's a good idea to be paired with signal processing.
2) Reactive web services. Preferably with spring-boot or vert.x but
3) I would also like to dive into golang (and make some reactive thing with it)
4) WebAssembly seems nice... But I got some concerns
5) exercise making wireframes -> CSS (with some js)
6) I've never really done any real backed work with nodejs, except serving and aot compiling js, or doing gulp tasks
7) Implementing a whole project, or a fraction of it as serverless on aws
* I'm definitely going to use a couple very simple services to make a docker swarm with load balancing, etc, just because I know how everything works but got no practical knowledge
8) Design an esports jersey for the university department I'm in (shouldn't take long)
So what do you guys think? Recommendations are welcome :)
P.S. last year in review:
> A webapp running on a raspberry pi powering a reflex testing game on gpio (java/spring-boot , codename: buttonmasher)
> small Elastic search cluster to monitor some random university servers through kibana dashboards
> laser tracking on wall of *any* colour and variable light conditions via a webcam (opencv) , controlling the mouse pointer, whether you run it against a projector or any wall
> Various random Photoshop stuff
Spending more time setting up tools and workflows like git, composer, docker, gulp etc etc etc than fucking coding anything! All this stuff was supposed to save time. And then these tools starts MESSING with each other!