# |
Jun 27th 2017, 10:16 |
neon1024 |
Badsauce. |
# |
Jun 27th 2017, 10:16 |
neon1024 |
The main point is, don’t compile it on production, especially on request |
# |
Jun 27th 2017, 10:15 |
neon1024 |
I’m sure it can be compiled using all sorts of tooling though |
# |
Jun 27th 2017, 10:15 |
neon1024 |
Yep |
# |
Jun 27th 2017, 10:15 |
birdy247 |
Right, so the RubyGem will "build" my sass into a .css file |
# |
Jun 27th 2017, 10:13 |
neon1024 |
Plus I have no experience of all this new fangled React, Angular api driven single page app stuff. I should learn that some time |
# |
Jun 27th 2017, 10:12 |
neon1024 |
My front-end is super rusty |
# |
Jun 27th 2017, 10:12 |
neon1024 |
Because back-end dev, I have to type stuff, check in browser, type more, check in browser :P |
# |
Jun 27th 2017, 10:11 |
neon1024 |
No, I have my IDE build a new CSS file everytime I type into the IDE |
# |
Jun 27th 2017, 10:11 |
birdy247 |
only when you want to change the css? |
# |
Jun 27th 2017, 10:11 |
neon1024 |
For Sass there is a GUI also, http://scout-app.io/ |
# |
Jun 27th 2017, 10:11 |
birdy247 |
When do you build it? |
# |
Jun 27th 2017, 10:10 |
neon1024 |
If you have PHP Storm you can have the IDE build the css for you also |
# |
Jun 27th 2017, 10:10 |
neon1024 |
With Grunt, not sure on that one sorry |
# |
Jun 27th 2017, 10:10 |
neon1024 |
With Sass you can for sure, the Ruby Gem has a --watch param on the CLI |
# |
Jun 27th 2017, 10:09 |
birdy247 |
I thought I could just build the stuff as and when you make changes to the sass files |
# |
Jun 27th 2017, 10:09 |
birdy247 |
Thats sounds worrying lol |
# |
Jun 27th 2017, 10:08 |
neon1024 |
I did this when I PR’d my local php usergroup website and broke everything :P |
# |
Jun 27th 2017, 10:08 |
neon1024 |
Do remember to put a commit hook in your repo to ensure Grunt script is run before you commit, so you can’t push stuff up which isn’t built |
# |
Jun 27th 2017, 10:07 |
neon1024 |
I guess it’s whatever is easy to install locally and you like the best :slightly_smiling_face: |
# |
Jun 27th 2017, 10:06 |
neon1024 |
¯\_(ツ)_/¯ |
# |
Jun 27th 2017, 10:06 |
neon1024 |
PHP with Composer |
# |
Jun 27th 2017, 10:06 |
neon1024 |
Ruby with Gem, or Node with NPM |
# |
Jun 27th 2017, 10:06 |
neon1024 |
So it’s 6 and two 3's |
# |
Jun 27th 2017, 10:06 |
neon1024 |
We use Sass, and build locally using the Ruby gem |
# |
Jun 27th 2017, 10:06 |
neon1024 |
Heh |
# |
Jun 27th 2017, 10:06 |
Antoniossss |
(I would use CDN for that) |
# |
Jun 27th 2017, 10:06 |
birdy247 |
and build with grunt |
# |
Jun 27th 2017, 10:06 |
birdy247 |
Was going to use less for the css |
# |
Jun 27th 2017, 10:05 |
neon1024 |
If you’re ‘building’ your assets, perhaps you need something like Grunt |
# |
Jun 27th 2017, 10:05 |
birdy247 |
seems fairly quick and easy to setup |
# |
Jun 27th 2017, 10:05 |
neon1024 |
I bet there are lots of funky NodeJS packages you can find on NPM for various things though :slightly_smiling_face: |
# |
Jun 27th 2017, 10:05 |
birdy247 |
but take your point |
# |
Jun 27th 2017, 10:05 |
birdy247 |
I use mapping fairly heavily |
# |
Jun 27th 2017, 10:04 |
neon1024 |
My staple is really just Twitter Bootstrap and jQuery :P |
# |
Jun 27th 2017, 10:04 |
neon1024 |
I guess if you use lots of front-end libraries you might find Bower more manageable. Like if you were building a single page app in React, Angular, Ember or something like that. Not something I’ve ever done. |
# |
Jun 27th 2017, 10:02 |
neon1024 |
Stuff like jQuery I pull from the Google CDN |
# |
Jun 27th 2017, 10:01 |
neon1024 |
Most JS libraries I use are on Packagist. So I install them with Composer and symlink them into /webroot |
# |
Jun 27th 2017, 10:01 |
birdy247 |
and then copy/paste it to an "assets" folder in webroot |
# |
Jun 27th 2017, 10:01 |
birdy247 |
I currently download something i.e. bootstrap |
# |
Jun 27th 2017, 10:01 |
birdy247 |
I mean the files |