Asset Finger Printing - Githubissues

jgoux / generator-angulpify

Yeoman generator involving AngularJS, Gulp and Browserify

138 stars 21 forks source link

Asset Finger Printing #22

Closed wlaurance closed 9 years ago

wlaurance commented 9 years ago

One thing I've found helpful, is to finger print all of the assets. This would have lots of benefits for development and production.

Do you know if there an easy way to get some sort of fingerprinting with the gulp/config.js file? I see there is a prefix option. If this is something that can be changed dynamically, that'd work I suppose.

Do you have any thoughts on how to support asset fingerprinting?

jgoux commented 9 years ago

Hello ! It's done in the next version. I'll upload it on a dev branch so you can start using it.

wlaurance commented 9 years ago

Oh awesome! Thanks @jgoux

wlaurance commented 9 years ago

Hey @jgoux can you push your dev branch?

Thanks!

jgoux commented 9 years ago

@wlaurance I updated the dependencies and it breaks some tasks (the sass one). I'll upload the dev branch this WE after I resolve this issue. ;)

jgoux commented 9 years ago

@wlaurance I just updated the dev branch. You can try it at your own risks :P Don't hesitate to report issues and make suggestions on the gitter page. ^^ The major changes are :

The project structure, following John Papa's style guide
Livereload not needed anymore, browser-sync to the rescue
You can add environments files which are compiled to angular constants (very useful for api links :D )
Assets finger printing (prod environment)
The script part is compiled into two files instead of one : vendors + your own app And some other stuff. I didn't have the time to add coffeescript/typescript/es6 support yet, it's my next step. ;) I have some sourcemaps problems to fix too.

jgoux commented 9 years ago

Feel free to reopen if you have bugs with the finger printing. ;)

wlaurance commented 9 years ago

Looks great! I've added a few things to my existing gulp tasks. What is the best way to pull in your changes? Obviously, this is a breaking change because of the new file layout. I suppose for now, I could just dump my existing tasks and move yours in. Do you have any recommendations for merging into an existing generated project?

jgoux commented 9 years ago

To test it you can install it from git://github.com:jgoux/generator-angulpify.git#dev in a package.json Merging an existing generated project seems complicated as I changed a lot of things. However, you can touch the config.js file inside the gulp directory to customize the tasks. (Each task config is in this file, as well as the project structure)