loganfsmyth

{
  sourceMaps: false,
  comments: false,
  plugins: [
    ["plg-one", {}],
    ["plg-two", {opt: false}],
  ],
  env: {
    development: {
      sourceMaps: true,

loganfsmyth

For explanation, essentially we'd generate a cache UUID based on cacheKey of your entire Babel config data and on all the plugin's cacheKeys, along with other stuff like the plugin options. Then we can take that cache key and fetch the cached data from wherever.

Each function in the cached block will be wrapped with logic to record the inputs and outputs, and the data will be stored in the output cacheable data. After a transform, we'd write Babel's normal output object, plus the data from the calls to the cached functions, and write it to some cache storage backend based on the final overall cacheKey.

When loading data from cache, we'll load the config and build the key as usually, and then before transforming anything, we try to load from the cache based on the config's key. Once the data is loaded from the cache, Babel itself will replay each call to a cached function, based on whatever the previous cached result had done. If they return matching values, we'll consider it a cache hit.

This s

loganfsmyth

const query = `SELECT \`id\` FROM foo;`;
   

loganfsmyth

var OriginalSource = require('webpack/lib/OriginalSource');

module.exports = function(source, map){
    var identifier = this._module.identifier();

    this.cacheable();

    var origMap = this.sourceMap ? new OriginalSource(source, identifier, map) : null;

    var strictPrefix = '"use strict";\n';

loganfsmyth

events: {
    'click .child': 'clickChildEvent'
},

// With jQuery
clickChildEvent: function(event){
    $(event.currentTarget).toggleClass('clicked');
},

// With Backbone.Native

loganfsmyth

Programming Achievements: How to Level Up as a Developer

This gist is part of a blog post. Check it out at:

http://jasonrudolph.com/blog/2011/08/09/programming-achievements-how-to-level-up-as-a-developer