What do you think the following code does?
function fn(msg, time) {
  setTimeout(function() {
    console.log(msg);
  }, time);
}
fn('it works', 1000);| presentation | |
| .title('My Great Presentation') | |
| .slide({ | |
| title: 'Learn About Borders', | |
| bullets: [ | |
| 'Thing 1', | |
| 'Thing 2', | |
| ], | |
| code: ['path/to/file.css', [2,4]] // path to file, lines to grab | 
What do you think the following code does?
function fn(msg, time) {
  setTimeout(function() {
    console.log(msg);
  }, time);
}
fn('it works', 1000);| <!doctype html> | |
| <script type="text/javascript"> | |
| //LZW Compression/Decompression for Strings | |
| var dic = ""; | |
| var LZW = { | |
| compress: function (uncompressed) { | |
| "use strict"; | |
| var i, | |
| dictionary = {}, | |
| c, | 
| killall ssh-agent; eval `ssh-agent` | 
This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.
In that post I talked about 3 main reasons for moving from require.js to webpack:
Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.