GithubHelp home page GithubHelp logo

leecade / fe Goto Github PK

View Code? Open in Web Editor NEW
15.0 4.0 3.0 8.79 MB

:dog: Provide Font-End 2017 Tech Stack and standalone build environment

License: MIT License

JavaScript 91.30% Shell 4.04% Batchfile 0.03% HTML 3.07% CSS 0.36% AppleScript 0.78% Ruby 0.42%

fe's Introduction

FE

FE Stack JavaScript Style Guide npm version npm version Circleci Appveyor Coveralls Slack

LOGO meaning: The golden retriever is a professional guard dog with a gentle temperament, strong, very smart and friendly to their caregivers.


NEW PLAN

0.1.x DEPRECATED

You can review the old project here and npm i fe -g still works.

1.0 WIP

Refactor for better engineering and new techs such as SSR.

BETA VERSION CHANGELOG

  • [0.1.21]

    • [Improve] Add auto publish hook
  • [0.1.20]

    • [default config] Change default public path to / to fix bundle url error in child-routing + browser router
    • [Bug] Fixes default behavior of touch to avoid undefined content
    • [Install script] Improve double refresh environment variable

Developer Guide

$ git clone
$ yarn # or npm i
$ yarn dev
$ npm link # you got the global `fe`

release

$ npm run build
$ npm version patch -m "bump version"
$ npm publish # auto bump version
# build the release pkg
$ yarn release # change the tar download url if you have another one

FE Stack

screenshot

Motivation

TODO

Install

Depends on

  • node 4+
  • npm 3+

*nix(OSX / Debian / Centos ...)

curl https://raw.githubusercontent.com/leecade/fe/master/scripts/install.sh -L -o - | sh

Recommend Chinese users

General install through node

npm install fe -g

OSX

TODO

$ brew install fe

use curl https://raw.githubusercontent.com/leecade/fe/master/scripts/install.sh -L -o - | sh fallback first

Windows

TODO

use npm i -g fe fallback first

Get started

The quickly and manual way

Just create a json file named fe.config.json(labeling the root location of your project)

$ touch fe.config.json

That's all that matters, now let's get started:

$ fe d # alias `fe dev`

Type Enter if requested to generate entry file

Now that we are in dev mode, you may edit the src/index.js with liveload supports.

Next, we initialize React environment:

$ npm init -y
$ npm i react react-dom -S

Following the react tutorial, we put some code in src/index.js

import React, { Component } from 'react'
import { render } from 'react-dom'
class HelloMessage extends Component {
  state = {
    name: 'FE Stack'
  }
  render() {
    return <div>Hello {this.state.name}</div>
  }
}
render(<HelloMessage name="Jane" />, document.getElementById('root'))

Great! It works. Next Step: we fetch some mock data:

$ mkdir -p mock/TaskList
$ touch mock/TaskList/index.js

Put the following code in mock/TaskList/index.js:

module.exports = [{
  method: 'GET',
  route: '/task-list',
  handler: {
    "data": [{
      "name": "task1"
    }, {
      "name": "task2"
    }]
  }
}]

Then restart fe d and update src/index.js:

import React, { Component } from 'react'
import { render } from 'react-dom'
class HelloMessage extends Component {
  state = {
    name: 'FE Stack',
    mockData: ''
  }
  componentDidMount () {
    fetch('/api/task-list')
        .then(res => res.json())
        .then(mockData => this.setState(Object.assign({}, this.state, { mockData })))
  }
  render() {
    return <div>Hello {this.state.name}, {JSON.stringify(this.state.mockData)}</div>
  }
}
render(<HelloMessage name="Jane" />, document.getElementById('root'))

See src/config/default.js for more information about fe.config.json

{
  "TITLE": "PAGE_TITLE",
  "HOST": "localhost",
  "HTTPS": false,
  "DEV_SERVER_PORT": 3000,
  "MOCK_PREFIX": "/_mock",
  "PROXY": {
    "/api": {
      "target": "http://localhost:3000/",
      "pathRewrite": {"^/api": "/_mock"}
    }
  },
  "inChina": true,
  "FE_CONFIG_FILE": "fe.config.json",
  "BUILD_DIR": "build",
  "CONFIG_DIR": "config",
  "MOCK_DIR": "mock",
  "PUBLIC_DIR": "public",
  "SRC_DIR": "src",
  "EMPTY_FILE": "config/empty.js",
  "TEMPLATE_FILE": "config/template.ejs",
  "ENTRY_FILE": "src/index.js",
  "POLYFILLS_FILE": "config/polyfills.js",
  "HTML_FILE": "public/index.html",
  "TEST_SETUP_FILE": "config/setupTests.js",
  "publicPath": ""
}

The right and concise way

$ fe init mydemo

Ecosystem FE Stack

$ fe list

Available official components

component name description
fe-reset CSS reset implementation in FE stack
fe-datepicker
fe-upload
fe-table
fe-pagination
fe-input
fe-select
fe-form
fe-modal
fe-button

Available official boilerplates

boilerplat name description
basic A basic boilerplate
redux redux+route4+immutable
mobx TODO
dva TODO
ant TODO
ant TODO

fe's People

Contributors

greenkeeper[bot] avatar hypatiah avatar leecade avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

fe's Issues

An in-range update of webpack-hot-middleware is breaking the build 🚨

Version 2.17.0 of webpack-hot-middleware just got published.

Branch Build failing 🚨
Dependency webpack-hot-middleware
Current Version 2.16.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As webpack-hot-middleware is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/webpack-hot-middleware-2.17.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • a689475 2.17.0
  • c3f18fa Merge pull request #174 from apexskier/patch-1
  • 9b6effe Allow client overlay styles to be customized

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Grunt 0.4 Release

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributorsβ€”we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

An in-range update of stylus-loader is breaking the build 🚨

Version 2.4.0 of stylus-loader just got published.

Branch Build failing 🚨
Dependency stylus-loader
Current Version 2.3.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As stylus-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/stylus-loader-2.4.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 6 commits .

  • 9611dcf 2.4.0
  • 98b7002 Add 2.4.0 to changelog
  • 21f48e0 Merge pull request #154 from mzgoddard/webpack-2-options
  • 4d30096 Bump webpack 2 version tested on travis
  • 8d08bac Add a bit to the README about using ?config with webpack 1
  • a235bd8 Add some help for configuring the loader with webpack 2

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of osenv is breaking the build 🚨

Version 0.1.4 of osenv just got published.

Branch Build failing 🚨
Dependency osenv
Current Version 0.1.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As osenv is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-eslint is breaking the build 🚨

Version 7.1.1 of babel-eslint just got published.

Branch Build failing 🚨
Dependency babel-eslint
Current Version 7.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-eslint is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 5 commits .

  • bc482f4 7.1.1
  • baeb99b chore(package): update dependencies (#422)
  • 2d587d6 append code frame on parse error (#418)
  • e7c9a03 chore(package): update babylon to version 6.13.0 (#420)
  • 971c8d6 chore(package): update eslint to version 3.9.1 (#419)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of gulp-cached is breaking the build 🚨

Version 1.1.1 of gulp-cached just got published.

Branch Build failing 🚨
Dependency gulp-cached
Current Version 1.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As gulp-cached is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 7 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-core is breaking the build 🚨

Version 6.24.0 of babel-core just got published.

Branch Build failing 🚨
Dependency babel-core
Current Version 6.23.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-core is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/babel-core-6.24.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...6698c1c Details

  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Thought on version control strategy

About the fe version

fe is designed to separate the build environment of differents Font-End tech stacks (like: React / Rxjs / Angular2 / Vue2 ...) from project dependency and manage workflow to improve develop experience.

There is only one bridge section fe.config.json between fe and project, to replace quikly switch different fe version, keep fe.config.json flexable and extendable, fe should cover each of projects, some default configure can be automatic written and other different configs show on doc and changelog.

Thinking about the differents between two project 0.1.0 and 0.2.0:

  • fe.config.json

  • other custom configs(webpack / babel)

  • boilerplate

  • component

An in-range update of pre-commit is breaking the build 🚨

Version 1.2.1 of pre-commit just got published.

Branch Build failing 🚨
Dependency pre-commit
Current Version 1.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As pre-commit is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 2 commits .

  • 7d6feb1 [dist] 1.2.1
  • 3ecafe0 [fix] chmod 0777 the newly created file; Fixes #88

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of minimatch is breaking the build 🚨

Version 3.0.4 of minimatch just got published.

Branch Build failing 🚨
Dependency minimatch
Current Version 3.0.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

minimatch is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… coverage/coveralls First build on greenkeeper/minimatch-3.0.4 at 12.808% Details,- βœ… ci/circleci Your tests passed on CircleCI! Details,- βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details,- ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details,- βœ… codecov/patch Coverage not affected when comparing fe5bfde...0253092 Details

Commits

The new version differs by 3 commits0.

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of execa is breaking the build 🚨

Version 0.5.1 of execa just got published.

Branch Build failing 🚨
Dependency execa
Current Version 0.5.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As execa is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/execa-0.5.1 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • e5598cf 0.5.1
  • 39a6e50 Document the timedOut error property
  • e96350d Reimplement missing features. Fixes #30 & #32 (#68)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of cross-env is breaking the build 🚨

Version 3.2.0 of cross-env just got published.

Branch Build failing 🚨
Dependency cross-env
Current Version 3.1.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As cross-env is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v3.2.0

<a name"3.2.0">

3.2.0 (2017-03-04)

Features

  • revamp: revamp the entire lib (backward compatible) (#63) (dad00c46)
Commits

The new version differs by 4 commits .

  • dad00c4 feat(revamp): revamp the entire lib (backward compatible) (#63)
  • e33a85c docs(README): Add doc for cross-var. (#58)
  • 5e590ec docs(README): added how to use cross-env to run npm sub-scripts (#53)
  • afdb2de docs(README): mention BashΒ onΒ Windows (#49)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of handlebars is breaking the build 🚨

Version 4.0.9 of handlebars just got published.

Branch Build failing 🚨
Dependency handlebars
Current Version 4.0.8
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

handlebars is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… coverage/coveralls First build on greenkeeper/handlebars-4.0.9 at 12.808% Details
  • βœ… ci/circleci Your tests passed on CircleCI! Details
  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details
  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...cf307ea Details

Commits

The new version differs by 10 commits.

  • 5ec78a8 v4.0.9
  • 5333f31 Update release notes
  • 8a836e2 Handlebars.compile() does not modify "options" anymore
  • cc554a5 Fix build in windows
  • ed879a6 Ensure LF line-edings in handlebars-template fixtures (*.hbs)
  • 2e21e2b Run integration test with node handlebars -a ... on Windows
  • bdfdbea Ensure LF line-edings in lexer-files (*.l)
  • b50ef03 Force LF line-endings for spec/artifacts
  • 6e6269f Use istanbul/lib/cli.js instead of node_modules/.bin/istanbul
  • 7378f85 Publish valid semver task independently of the branch

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-cli is breaking the build 🚨

Version 6.24.1 of babel-cli just got published.

Branch Build failing 🚨
Dependency babel-cli
Current Version 6.24.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-cli is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/babel-cli-6.24.1 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details

  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...a7c9aba Details

  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of autoprefixer is breaking the build 🚨

Version 6.7.3 of autoprefixer just got published.

Branch Build failing 🚨
Dependency autoprefixer
Current Version 6.7.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As autoprefixer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • βœ… coverage/coveralls First build on greenkeeper/autoprefixer-6.7.3 at 12.808% Details

  • ❌ ci/circleci Your tests failed on CircleCI Details

Release Notes 6.7.3
  • Fix compatibility with β€œIntrinsic & Extrinsic Sizing” spec update.
Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

thoughts on boilerplate & generate design

currently download from github export master zip

Planning to switch to npm pkg because:

  1. version control
  2. generate tasks integration

but npm download slowly, try to direct download the tar pkg

common generate tasks (add mock) provided by fe module and others within boilerplates:

  • boilerplate directory structure:
package.json
meta.js
index.js
boilerplate/
generate/
  • index.js includes tasks scripts:
export default {
    'generate:component': env => {
       copy('folder', 'project/src')
    },
    'build:XXX': () => {
    }
};
  • export tasks in packge.json way
{
  "main": "index.js"
}

An in-range update of yargs is breaking the build 🚨

Version 6.4.0 of yargs just got published.

Branch Build failing 🚨
Dependency yargs
Current Version 6.3.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As yargs is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v6.4.0

Bug Fixes

  • locales: correct some Russian translations (#691) (a980671)

Features

Performance Improvements

  • normalizing package data is an expensive operation (#705) (49cf533)
Commits

The new version differs by 10 commits .

  • bf6707e chore(release): 6.4.0
  • 8507390 chore: add camelcase to greenkeeper ignore, until we drop 0.10 support (#704)
  • 49cf533 perf: normalizing package data is an expensive operation (#705)
  • 8f4c7cf docs: nit, make test description reflect API, not application of API
  • 21b74f9 feat: yargs is now passed as the third-argument to fail handler (#613)
  • 54cb31d feat: update to yargs-parser that addresses #598, #617 (#700)
  • 8bbca63 chore(package): update cross-spawn to version 5.0.1
  • a980671 fix(locales): correct some Russian translations (#691)
  • 68dac1f feat(locales): Added Belarusian translation (#690)
  • 46ce1bb feat(locales): Create nl.json (#687)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-loader is breaking the build 🚨

Version 6.3.0 of babel-loader just got published.

Branch Build failing 🚨
Dependency babel-loader
Current Version 6.2.10
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As babel-loader is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/babel-loader-6.3.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v6.3.0

πŸš€ New Feature

Allow to override BABEL_ENV/NODE_ENV at loader-level. Useful for isomorphic applications which have separate babel config for client and server.

πŸ› Bug Fix

  • Update loader-utils dependency to ^0.2.16 to fix compatibility with webpack 2 (#371) @leonaves

πŸ’… Polish

  • Improve FS caching to do less sync calls which improves performance slightly (#375) @akx
Commits

The new version differs by 10 commits .

  • 877e956 6.3.0
  • 4b3bafa FS caching improvements (#375)
  • 0b19a6d Update loader-utils dependecy to ^0.2.16 (#371)
  • 15881f4 Add env query parameter. (#368)
  • e9e3702 Update yarn.lockk
  • 707f31c chore(package): update eslint-config-babel to version 6.0.0 (#360)
  • 5657f48 chore(package): update eslint-config-babel to version 5.0.0 (#359)
  • 757002a Remove plugin-babel (#358)
  • a7e16da Update eslint-config-babel to the latest version πŸš€ (#357)
  • 3900952 Update CHANGELOG.md

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of request is breaking the build 🚨

Version 2.79.0 of request just got published.

Branch Build failing 🚨
Dependency request
Current Version 2.78.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As request is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/request-2.79.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 19 commits .

  • ff729c6 Update changelog
  • 3a98820 2.79.0
  • ab94c86 Merge pull request #2368 from forivall/patch-1
  • 95b12d0 Merge pull request #2394 from SimenB/files
  • d05c86c Use files in package.json
  • 9f702bf Merge pull request #2463 from lostcolony/master
  • 7532634 Remove redundant code
  • d16bf18 Merge branch 'master' into aws4-session
  • 67c9673 Merge pull request #2467 from simov/bump-uuid
  • 39350ed Bump uuid
  • e1c0981 Merge branch 'defunctzombie-uuid' of github.com:antialias/request into bump-uuid
  • 9122f43 Fixing requests/requests issue #2462 - AWS support does not include the use of session tokens for temporary credentials
  • 0131e2d Merge pull request #2459 from request/greenkeeper-taper-0.5.0
  • 8c6fd17 Merge pull request #2448 from mscdex/improve-new-test-reliability
  • 17095d5 chore(package): update taper to version 0.5.0

There are 19 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of babel-polyfill is breaking the build 🚨

Version 6.26.0 of babel-polyfill just got published.

Branch Build failing 🚨
Dependency babel-polyfill
Current Version 6.23.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

babel-polyfill is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… coverage/coveralls First build on greenkeeper/babel-polyfill-6.26.0 at 12.808% Details
  • βœ… ci/circleci Your tests passed on CircleCI! Details
  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details
  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...ac88d2d Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of object-assign is breaking the build 🚨

Version 4.1.1 of object-assign just got published.

Branch Build failing 🚨
Dependency object-assign
Current Version 4.1.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As object-assign is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 9 commits .

  • a89774b 4.1.1
  • 2915ed4 Add inline MIT license with @license marker (#45)
  • ba4ebc4 pin XO
  • 6627d98 Add note encouraging built-in use (#41)
  • f64a833 Store a reference to Object.getOwnPropertySymbols (#39)
  • 022fe39 Add built-in Object.assign benchmarks (#40)
  • ea6846a meta tweaks
  • 066439e add missing test for target being a primitive (#34)
  • 5174655 fix XO lint issues

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Reduce the size of install pkg

The idea is use webpack pack each command js and their deps in single file, then remove deps relation in package.json avoid auto install again.

some modules (which require node-gyp) as externals will build after install.

some config file(which load async) compile as standalone file.

remove .md in node_modules.

An in-range update of rimraf is breaking the build 🚨

Version 2.6.2 of rimraf just got published.

Branch Build failing 🚨
Dependency rimraf
Current Version 2.6.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

rimraf is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… coverage/coveralls First build on greenkeeper/rimraf-2.6.2 at 12.808% Details
  • βœ… ci/circleci Your tests passed on CircleCI! Details
  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...c710fcd Details
  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details

Commits

The new version differs by 2 commits.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of inquirer is breaking the build 🚨

Version 1.2.3 of inquirer just got published.

Branch Build failing 🚨
Dependency inquirer
Current Version 1.2.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As inquirer is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v1.2.3
  • Fix bug with editor prompt #442
Commits

The new version differs by 4 commits .

  • ac8b564 1.2.3
  • a78dbac Dispose events.line subscription properly for editor questions. Fixes #442. (#451)
  • 5a73a88 Add node 7 and drop node 5 from travis coverage
  • f540851 Documentation Examples (#444)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of vinyl is breaking the build 🚨

Version 2.0.2 of vinyl just got published.

Branch Build failing 🚨
Dependency vinyl
Current Version 2.0.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As vinyl is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/vinyl-2.0.2 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Release Notes v2.0.2

Fix

  • Proxy cwd if base is set to same value (07e4093) - Closes #129
Commits

The new version differs by 2 commits .

  • e014ed1 Release: 2.0.2
  • 07e4093 Fix: Proxy cwd if base is set to same value (fixes #129)

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of consolidate is breaking the build 🚨

Version 0.14.3 of consolidate just got published.

Branch Build failing 🚨
Dependency consolidate
Current Version 0.14.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As consolidate is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of whatwg-fetch is breaking the build 🚨

Version 1.1.0 of whatwg-fetch just got published.

Branch Build failing 🚨
Dependency whatwg-fetch
Current Version 1.0.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As whatwg-fetch is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 48 commits .

  • 76f6a09 fetch 1.1.0
  • 08e6a85 Attach FileReader event handlers before calling its read* method
  • a8695f9 Merge branch 'array-buffer'
  • abfe072 Shorten body extraction tests
  • 9a703ba ArrayBuffer can now be consumed through blob()/text()
  • 9a04a06 Share identical tests between Request & Response
  • 7f55e03 Remove duplicate test
  • 578784e Simplify ArrayBuffer tests
  • 7021a0c Merge branch 'master' into array-buffer
  • 4949171 Define npm test script
  • 5f9254f Remove Bower dependency in development
  • 5fd8402 Default Response status is 200 OK
  • 4528229 Merge pull request #430 from mislav/array-buffer-view
  • 211d5ca Support ArrayBuffer in BodyInit
  • 25f7646 Test against PhantomJS 2.1.1 on Travis

There are 48 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of html-webpack-plugin is breaking the build 🚨

Version 2.26.0 of html-webpack-plugin just got published.

Branch Build failing 🚨
Dependency html-webpack-plugin
Current Version 2.25.0
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As html-webpack-plugin is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/html-webpack-plugin-2.26.0 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • d22c230 Allows events to add no-value attributes
  • 90c6b90 Add yarn lock file
  • f3abe9f Update dependencies

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of espower is breaking the build 🚨

Version 2.0.1 of espower just got published.

Branch Build failing 🚨
Dependency espower
Current Version 2.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As espower is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 5 commits .

  • 6350083 2.0.1
  • dfe87c3 docs(CHANGELOG): add CHANGELOG for 2.0.1
  • 869ed49 Merge pull request #34 from power-assert-js/arrow-function-with-concise-body
  • 19d2a78 fix(espower): use upper block when assertion is a concise body of ArrowFunctionExpression
  • 02900d5 chore(travis): gulp is installed locally

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of updtr is breaking the build 🚨

Version 0.2.3 of updtr just got published.

Branch Build failing 🚨
Dependency updtr
Current Version 0.2.2
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As updtr is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci Your tests are queued behind your running builds Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • 7d3402f v0.2.3
  • ea8c41b Merge pull request #50 from robertknight/report-missing-module-names
  • ebd2c11 Report the names of missing modules

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of filesize is breaking the build 🚨

Version 3.5.7 of filesize just got published.

Branch Build failing 🚨
Dependency filesize
Current Version 3.5.6
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

filesize is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details - βœ… **coverage/coveralls** First build on greenkeeper/filesize-3.5.7 at 12.808% [Details](https://coveralls.io/builds/11303924),- βœ… **ci/circleci** Your tests passed on CircleCI! [Details](https://circleci.com/gh/leecade/fe/330?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link),- βœ… **continuous-integration/appveyor/branch** AppVeyor build succeeded [Details](https://ci.appveyor.com/project/leecade/fe/build/1.0.363),- ❌ **codecov/project** 12.31% (-0.5%) compared to fe5bfde [Details](https://codecov.io/gh/leecade/fe/commit/e10a0f70a8101d2da7e1f452e738fba25746b7f8),- βœ… **codecov/patch** Coverage not affected when comparing fe5bfde...e10a0f7 [Details](https://codecov.io/gh/leecade/fe/commit/e10a0f70a8101d2da7e1f452e738fba25746b7f8)

Commits

The new version differs by 1 commits0.

  • 2edf1a3 Adding babili task to minify the es6 file, fixes #86

false

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of standard is breaking the build 🚨

Version 8.6.0 of standard just got published.

Branch Build failing 🚨
Dependency standard
Current Version 8.5.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As standard is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 10 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of detect-port is breaking the build 🚨

Version 1.2.0 of detect-port just got published.

Branch Build failing 🚨
Dependency detect-port
Current Version 1.1.4
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

detect-port is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ

Status Details
  • βœ… coverage/coveralls First build on greenkeeper/detect-port-1.2.0 at 12.808% Details
  • βœ… ci/circleci Your tests passed on CircleCI! Details
  • βœ… continuous-integration/appveyor/branch AppVeyor build succeeded Details
  • ❌ codecov/project 12.31% (-0.5%) compared to fe5bfde Details
  • βœ… codecov/patch Coverage not affected when comparing fe5bfde...9e8884a Details

Commits

The new version differs by 1 commits.

  • 4a9e127 cli tweak to verbose (#25)

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of gulp-standard is breaking the build 🚨

Version 8.0.4 of gulp-standard just got published.

Branch Build failing 🚨
Dependency gulp-standard
Current Version 8.0.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As gulp-standard is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details

  • ❌ ci/circleci Your tests failed on CircleCI Details

Commits

The new version differs by 3 commits .

  • 3e434a2 chore: version bump
  • 8b89053 Merge pull request #27 from stevelacy/master
  • d51dbaf Contune the stream through a reporter - closes #26

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of react-hot-loader is breaking the build 🚨

Version 3.0.0 of react-hot-loader was just published.

Branch Build failing 🚨
Dependency react-hot-loader
Current Version 3.0.0-beta.7
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

react-hot-loader is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/appveyor/branch Waiting for AppVeyor build to complete Details
  • ❌ ci/circleci Your tests failed on CircleCI Details

Release Notes v3.0.0
  • Add React 16 support (#629, #658)
  • Remove RedBox as default error catcher (#494)
Commits

The new version differs by 86 commits.

  • 5973747 Merge pull request #658 from gaearon/react-16
  • 80136ac v3.0.0
  • 7a968b6 refactor: revert HotContainer for now
  • 6d0346f feat: expose AppContainer with warning
  • 7d0e0da docs: remove coverage badge
  • 429cc4a docs: improve README
  • 3338ce2 feat: React 16 compatibility
  • 47ccb0a Merge pull request #655 from theKashey/master
  • b964851 document HOC Troubleshooting
  • 00404dd docs: keep AppContainer in doc
  • 60503a7 Merge pull request #639 from gaearon/hot-container
  • 7d1d294 Rename AppContainer into HotContainer
  • 2679e73 Merge pull request #494 from gaearon/no-redbox
  • 31fba04 Remove RedBox as default error catcher
  • ac52cd9 Merge pull request #608 from theKashey/master

There are 86 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of coveralls is breaking the build 🚨

Version 2.11.16 of coveralls just got published.

Branch Build failing 🚨
Dependency coveralls
Current Version 2.11.15
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As coveralls is β€œonly” a devDependency of this project it might not break production or downstream projects, but β€œonly” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • ❌ ci/circleci CircleCI is running your tests Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 13 commits .

  • 8dfcfd6 version bump
  • 4bc93ac Merge branch 'master' of github.com:nickmerwin/node-coveralls
  • 671acca removed codeship badge
  • f390392 Merge pull request #152 from ndaidong/master
  • de968b0 Merge pull request #147 from hyperlink/update-request-dep
  • 72a4046 Merge pull request #154 from a0viedo/patch-1
  • 87b27f7 Merge pull request #142 from Hirse/feature/travis-pr
  • 3edbecb Merge pull request #155 from kasperlewau/master
  • d117e3d reenable drone
  • dd230f6 don't hardcode minor version
  • cc0882d Update outdate dependencies
  • 99edf1a Fix node-uuid deprecation by updating request dependency
  • f94b647 Get PR number from TRAVIS

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of debug is breaking the build 🚨

Version 2.3.2 of debug just got published.

Branch Build failing 🚨
Dependency debug
Current Version 2.3.1
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

As debug is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this πŸ’ͺ


Status Details
  • βœ… coverage/coveralls First build on greenkeeper/debug-2.3.2 at 12.808% Details

  • βœ… ci/circleci Your tests passed on CircleCI! Details

  • ❌ continuous-integration/appveyor/branch AppVeyor build failed Details

Commits

The new version differs by 3 commits .

  • 1c6f458 Release 2.3.2
  • 56fd336 be super-safe in index.js as well
  • 0b6ca27 fix(browser): should check whether process exists

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.