jaredpalmer

import React from 'react';
import debounce from 'utils/debounce';

class EmailInput extends React.Component {
  checkEmail = value => {
    // only check if the field passes Yup email validation first
    if (
      !this.props.form.errors[this.props.name].includes(
        'invalid' /* or whatever your error message is*/
      )

franklinjavier

• cmd+k z -> zen mode
• cmd+\ -> side-by-side
• cmd+b -> toggle sidebar
• cmd+shift+m -> problems panel
• ctrl+j -> join line

loiane

Ingredientes

• Foto: https://www.instagram.com/p/BJleLGRgv0V

Bolo

• 3 ovos
• 1/3 xic açúcar
• 1/2 xic trigo
• 1/2 col chá fermento químico
• 3/4 a 1 xic morangos picados

subfuzion

Common Options

-#, --progress-bar Make curl display a simple progress bar instead of the more informational standard meter.

-b, --cookie <name=data> Supply cookie with request. If no =, then specifies the cookie file to use (see -c).

-c, --cookie-jar <file name> File to save response cookies to.

xjamundx

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:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

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.

renegare

/**
 * testing tasks (using karma to test in the browser). Requires a karma.conf.js for full config
 * single-run testing 
 * continuous testing
 */

/** base deps, but you may need more specifically for your application */
var gulp = require('gulp');
var gutil = require('gulp-util');
var path = require('path');