Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Javascript Apps at Build Artifacts


Published on

Talk at EmpireJS 2014. May 6, 2014.

Published in: Technology
  • Be the first to comment

Javascript Apps at Build Artifacts

  1. 1. CLAY SMITH Javascript apps as a build artifact @smithclay May 6, 2014 at EmpireJS
  2. 2. This is my brain on Javascript.
  3. 3. From the “Javascript Development Workflow” talk Understanding it all (from @paulirish)
  4. 4. Easy answer: We’re using Javascript written for the web more and in different places. Why does it matter? From 4/13 to 4/14,
  5. 5. Now for a 5-minute Overview of the Raging Javascript Battles of Today
  6. 6. Javascript Battlefield #1 (2010-present) “My framework is better than yours.” of_JavaScript_frameworks
  7. 7. from Jake Brunch smoosh anvil.js Grunt Gear.js buildr mimosa modjs automaton james.js Bud Gulp simplebuild Brocolli Fez Javascript Battlefield #2 (2011-present) “My build tool is better than yours.”
  8. 8. “I prefer to write in _____(A)______, it makes creating _____(B)______ easier.” (*)script Battlefield #3 (2010-present) Coffeescript ClojureScrip t Dart TypeScript asm.js GWT dogescript A B web apps mobile apps frameworks nodebots arduinos much wow
  9. 9. Javascript Battlefield #4 (2012-present) “My dependency management tool is better than yours.” bower component.js favorite package:
  10. 10. The easiest way to have a 30-minute conversation at a Javascript conference. We’ve all chosen sides. • Many Javascript libraries for a web app. • Many dependency managers for libraries. • Build tools that use dependency managers (written in JS or another language). • Many dependencies of the build tools (that might use another dependency manager) • Many source languages. • Many different types of target platforms.
  11. 11. “Just the essential libraries” A single-page Javascript application c. 2014 PagerDuty Mobile,
  12. 12. Here’s the ones PagerDuty uses with gulp. Plugin-ify your JS build tools (2012-present)
  13. 13. When you realize you need to make it work in mobile web views.
  14. 14. A JavaScript apps running in mobile web browsers or embedded in native apps. The mobile (web) frontier (2007-present)
  15. 15. Put all the things in git (or any VCS) Attempt #1 • well understood workflow (just commit!) • “easy” mobile builds - git clone to see JS source • git submodule purgatory (whoops, I forgot!) • merge conflict hell (Pull Requests broken) • compiled, concatenated, transformed code in VCS (not good) Good: Bad:
  16. 16. Some cool kids are doing it. This is a popular approach for many JS libraries
  17. 17. Well… how about using ? Attempt #2 • well-understood workflow (npm install FTW) • represents an ideal of JS dependency management • gives us a way to avoid git submodules and get *.min.js files out of source control
  18. 18. kudos: npm mentions it in the docs “The advantage of doing [compilation, transformation, etc] at prepublish time instead of preinstall or install time is that they can be done once, in a single place, and thus greatly reduce complexity and variability. Additionally, this means that: You can depend on coffee-script as a devDependency, and thus your users don't need to have it installed.” Warning! May not do what you expect!
  19. 19. (Since we were working with private code) npm module from private github repo (we cheated and tried to use git) ^ package.json in our XCode project that pulls our JS app code
  20. 20. npm that pulls a package from git didn’t get us all the way there Sadly… • we need to check in the transformed JS code (and css, and HTML) • we introduce lots of complexity into (native) builds processes. XCode suddenly needs to know how to gulp (or grunt). If we want simple native application build…. If we don’t want to check in transformed code…
  21. 21. Overly simplified misleading diagram. Is there another way?
  22. 22. build artifact (n) - one of many kinds of tangible by-products produced during the development of software. Our production JavaScript app looks like a build artifact
  23. 23. Build artifacts are happiest in build artifact repository managers. The app needs a home
  24. 24. Github Release API as a pseudo-artifact repository Attempt #3 - success! • A “release” in GitHub is just a tag and an collection of binary blobs stored on S3. • API Access Only (need to generate a token). • simplifies native mobile builds (only curl and unzip required).
  25. 25. Uploading a ZIP archive with a single index.html to GitHub’s Release API
  26. 26. No (gulp||grunt) plugin? Stream-ify it. The node.js streaming API is incredible.
  27. 27. Then, add a build step in XCode/Android Studio that fetches build artifacts ^ Thanks to @alperkokmen
  28. 28. Is there (or should there be) a better tool out there? It’s a decent option for hybrid apps * Sonatype Nexus -> NPM bridge * Private NPM/“CommonJS Repositories” that are optimized for build artifacts? * [insert your solution here]
  29. 29. Thank you. Clay Smith @smithclay Don’t check-in *.min.js files please. build/