Skip to content

Instantly share code, notes, and snippets.

View Smolations's full-sized avatar

Chris Smola Smolations

  • Recurly
  • Superior, CO
View GitHub Profile
@Smolations
Smolations / epoxy_help.md
Created September 22, 2017 22:29
`npm run help` in epoxy
$ npm run help

> epoxy@0.41.2 help /home/vagrant/polymer/epoxy
> npm run & gulp help

Lifecycle scripts included in epoxy:
  postinstall
    jspm install
  start
@Smolations
Smolations / elmer_help.md
Created September 22, 2017 22:27
`npm run help` in elmer
$ npm run help

> @tangogroup/elmer@1.0.0 help /home/vagrant/polymer/elmer
> npm run & gulp help

Lifecycle scripts included in @tangogroup/elmer:
  start
    webpack-dev-server --config webpack.toolkit.config.js --open
  test
var path = require('path');
module.exports = {
entry: {
toolkitStandalone: ['./src/main.es6.js'],
},
devtool: 'source-map',
output: {
path: path.resolve('./dist'),
library: '[name]',
@Smolations
Smolations / gulpfile.js
Created August 16, 2017 19:16
Gulpfile
gulp.task('components:toolkitStandalone:js', 'builds the components toolkit javascript', ['doc-gen', 'components:components:css', 'components:toolkit:css'], () => {
const webpack = require('webpack-stream');
return gulp.src(`${paths.src.components}components.es6.js`)
.pipe(webpack(require('./webpack.toolkit.config.js')))
.pipe(gulp.dest(paths.dest.dist));
});
@Smolations
Smolations / error.txt
Created August 16, 2017 19:10
TypeError: item.node is not a function
/home/vagrant/project/my-components/node_modules/webpack-sources/lib/ConcatSource.js:37
return typeof item === "string" ? item : item.node(options);
^
TypeError: item.node is not a function
at /home/vagrant/project/my-components/node_modules/webpack-sources/lib/ConcatSource.js:37:50
at Array.map (native)
at ConcatSource.node (/home/vagrant/project/my-components/node_modules/webpack-sources/lib/ConcatSource.js:36:63)
at /home/vagrant/project/my-components/node_modules/webpack-sources/lib/ConcatSource.js:37:50
at Array.map (native)
@Smolations
Smolations / main.es6.js
Created August 16, 2017 19:06
Module entry point
// import 'angular-sanitize'; // eslint-disable-line import/no-extraneous-dependencies, import/no-unresolved, import/extensions, no-unused-vars
// import angular from 'angular';
// import ngAnimate from 'angular-animate'; // eslint-disable-line import/no-extraneous-dependencies, import/no-unresolved, import/extensions
// import uiRouter from '@uirouter/angularjs'; // eslint-disable-line import/no-extraneous-dependencies, import/no-unresolved, import/extensions
// import componentsModule from './components.es6';
// import '../dist/components.css!'; // eslint-disable-line import/no-webpack-loader-syntax, import/no-unresolved
// import componentsToolkit from './toolkit/module.es6';
// import '../dist/toolkit.css!'; // eslint-disable-line import/no-webpack-loader-syntax, import/no-unresolved
@Smolations
Smolations / angular-styleguide-polymer-reqs.md
Last active November 11, 2018 14:48
Angular Styleguide Goodies for Polymer

This document was created by modifying John Papa's README.md at his GitHub project. All references to "me," "my," etc. refer to him.

Devs listed in the checkbox groups should go through each style suggestion, and check off those styles which they agree with, even partially. ONLY LEAVE A CHECKBOX UNCHECKED IF YOU COMPLETELY DISAGREE WITH THE STYLE SUGGESTION. If you only partially agree, leave a comment referencing the style number (e.g. Y271) and it will be addressed in the sync which will occur after every dev has reviewed the document.

Keep in mind that some of these things we already do, while others we already partially do. This document may eventually end up in the handbook so it will act as an all-encompassing styleguide for us.

Angular Style Guide

Opinionated Angular style guide for teams by John Papa

@Smolations
Smolations / gist:beb38a84f1de0fcf059b
Created January 13, 2015 21:50
Fix Flagger Floundering
# assume that model params are not automatically added to a controller's
# @params. this will allow for more flexibility for the current endpoint
# implementation. they can, however, be stored somewhere on the controller
# so that these blocks below can explicitly state whether or not they should
# be available for use in a route
# media_controller example
resource do |r|
# r.class == Flagger::Controller