Kurtis Rainbolt-Greene

I love the word coordinates, but you're right `#spots_by_lat_lng` is more effective signaling.

Well if you start sharing the icons as asked in #5 it would be nice to import individual icons into a project: ``` require("node_modules/css-icons/css/print.css") ```

Not quite, since I actually use gulp for css compiling. See here: ``` gulp.task("styles", () => { return gulp.src([ "./node_modules/font-awesome/css/font-awesome.css", "./node_modules/normalize.css/normalize.css", "./source/client/index.css" ]) .pipe(gulpConcat("./transpiled/index.css")) .pipe(gulpMyth()) .pipe(gulpSize({showFiles: true})) .pipe(gulp.dest(DESINATION)) .pipe(gulpGzip({append: true}))...

An npm package doesn't have to have a command. It's for sharing things! If you share this via npm then I can use these icons in my project.

You can do the whole app, but it might be beneficial to narrow it down to a select list of files using `.npmignore`. It works the same as `.gitignore`.

The only failing bit is node 0.10, which frankly...it's way past lts.

I think overall this is a good design philosophy and cracks another big boulder of throttling.

Fun fact: 3 of the dependencies that you install store files in `stable-diffusion/src/` and if you don't cache those files you have to reinstall every time.

@JustinGuese Will do when I have time. It's the CLIP and taming-transform dependency that make files in `src/`.

Oh also, don't run `conda env update` because it will update libraries past what works.