Giter Club home page Giter Club logo

quik's Introduction

Quik

A quick way to prototype and build apps with React and Babel with zero-setup.

semantic-release npm version build status coverage status dependencies license

Setting up the tooling required to work on a modern day web app is hard, and makes quick prototyping much more difficult than it should be. Quik is a quick way to prototype a React application without any kind of setup. It can also generate a production-ready JavaScript bundle to use in your app. No setup required.

Quik runs a simple server that compiles JavaScript files with Babel on the fly, so you can include ES201x files in a script tag directly,

<script src="index.js"></script>

Tip: You can add ?transpile=false to the script src to skip the transpilation.

Quik also exposes a koa middleware which can be easily integrated with your server.

Features

  • One-time installation, no additional setup required
  • Hot Module Replacement
  • Generates bundles for use in production
  • Generates single standalone HTML file for sharing
  • React, Redux, React Router and Radium are already included
  • Quick prototyping with an optional starter template

Installation

You need at least Node 7.0 to run quik.

npm install --global quik

Usage

Open the Terminal in any directory and run the following,

quik

It'll start a simple server which will serve the files in the current directory. By default, it'll automatically watch the file index.js if present.

If no index.html file is present, it'll generate and serve an HTML file with it's script tag pointing to index.js file. Alternatively, you can specify the name of the script to include,

quik --run script.js

If you want to use a different port. For example, to run the server in the port 8008, run,

quik --port 8008

You can include any ES2015 file in a script tag in an HTML file and the script will be transpiled to ES5 on the fly. You can use JSX and Flow syntax as well as use ES2015 modules to import other scripts. It just works.

NOTE: You'll need to install any dependencies you use in the project manually.

Enabling Hot Module Replacement

Hot Module Replacement for React Components is automatically enabled if you have a script named index.js in the directory, or if you specified a script to run with the --run option, for example,

quik --run app.js

Alternatively, you can specify the filenames you want to watch for HMR,

quik --watch file1.js file2.js

When using the --run option, the index.html file is always generated on the fly and served. If you want to use your own index.html file, just use --watch.

You only need to specify the entry points, not all scripts. Most of the time it'll be just one script. Note that Hot Module Replacement won't work for any components in the entry points.

Generating JavaScript Bundle

The bundler provides an abstraction on top of webpack with sensible defaults for a React project. If you need additional customisation, use webpack directly for bundling.

To generate a bundle wth quik for use in your web application, run the following in a Terminal,

quik --bundle entry.js --output bundle.js --production

The --production option performs minification on the resulting bundle. You can omit it if you're not going to use the file in production.

You can provide multiple entry points as arguments. In that case, you can use [name] to get the name of the entry point while specifying an output file,

quik --bundle file1.js file2.js --output [name].bundle.js --common common.bundle.js

Sourcemap files are automatically generated when generating bundles.

Generating a sharable single HTML file

Sometimes you might want compile and inject bundles into an HTML file for easier sharing through dropbox, email etc. To do so, run the following in a Terminal,

quik --html --output output.html --production

You can also specify an HTML file, which quik will parse for any local scripts. Then it will build them and inject into the HTML file. It'll also inline stylesheets as is, without any pre-processing. Just open the generated HTML file in any browser to preview.

quik --html index.html --output output.html

Specify browser to open

You can specify which browser to open when server starts. Refer opn's documentation on browser names.

For example, to use firefox as the browser, you'd do,

quik --browser firefox

Sample project

To get started with a sample project, run the following in a Terminal,

quik --init AwesomeProject
cd AwesomeProject && quik

Refer the API documentation for more to know how to customize and extend the server.

How it works

The quik middleware is just an abstraction on top of webpack. It includes a base webpack config and generates appropriate config files when needed. For example, when the quik server receives a request for a JavaScript file, it generates a webpack config on the fly, the file is then transpiled with webpack, and the server responds with the generated bundle instead of the original script.

Motivation

Tooling is the hardest part in JavaScript development, and it's time we do something about it.

The following posts inspired me to work on quik,

One good thing about quik is that it is highly opinionated, which means we don't worry about becoming generic and can focus on making it better at what it does. It doesn't allow additional babel transforms, or loaders for webpack as of now.

Inline styles are recommended for styling. When combined with a library like radium, they provide much more flexibility than CSS.

The goal of quik is to improve the tooling around React and Babel projects. While it'll be easy enough to support additional customization, it defeats the whole purpose of being zero-setup. If you need additional configuration, it will be better to go with webpack directly. If you think something should be included by default, send a pull request or file a bug report.

Even though quik itself doesn't provide additional customization, it's just a koa middleware at the core. That means it's composable with other koa middlewares and you can add additional functionality easily.

Plans for improvements

Below are some ideas on how to improve quik. It would be awesome to receive pull requests for these.

  • Automatically parse HTML files to enable hot reloading without having to specify files with --watch
  • Cache bundles instead of re-building on every request
  • Better error handling
  • Atom plugin to make it easier to use without CLI

Similar tools

Of course, quik is not the only tool trying to solve this problem. There are few other tools which are also doing a great job at it.

  • react-heatpack - a very minimal prototyping server for React with Hot Module Replacement
  • nwb - similar, but has lot more options
  • rwb - pretty similar to quik, has Hot Module Replacement and can also build bundles for production
  • run-js - works on top of browserify, zero-setup, has live-reload functionality

quik's People

Contributors

greenkeeperio-bot avatar jestho avatar lsanwick avatar satya164 avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar  avatar

quik's Issues

Babel 7

Hey there! I like your plugin and recently tried it in a previous project. Now, I am trying to use it again however it looks like it does not currently support Babel 7 (I get an error of cannot read property loose of undefined). Any plans on updating? Thanks!

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

Version 6.26.0 of babel-cli just got published.

Branch Build failing 🚨
Dependency babel-cli
Current Version 6.24.1
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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 🌴

Specify the browser

Can I specify the browser(firefox, chrome, etc...) when starting quik as setting file or cli option?

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

Version 1.1.0 of del-cli just got published.

Branch Build failing 🚨
Dependency del-cli
Current Version 1.0.0
Type devDependency

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

As del-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 🌴

Hide uglify warnings

Would you be interested in a PR that hides the uglify warnings when bundling/inlining html?

They're noisy and not really helpful.

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

Version 4.0.5 of less-loader just got published.

Branch Build failing 🚨
Dependency less-loader
Current Version 4.0.4
Type dependency

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

less-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes Release v4.0.5

4.0.5 (2017-07-10)

Chore

Commits

The new version differs by 2 commits.

  • 670ab18 chore(release): 4.0.5
  • 643c00b chore: update peer dependencies to support webpack 3 (#208)

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 🌴

Webpack v2.1.0-beta.23 and later breaks quik

If you refer to webpack/webpack#3018 , it seems there was a breaking change in how webpack validates configuration objects. I was able to get quik to work by forcing it to use v2.1.0-beta.22, however a smarter person than I will have to figure out how to adjust how quick is using webpack's configuration object.

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

Version 7.1.0 of autoprefixer just got published.

Branch Build failing 🚨
Dependency autoprefixer
Current Version 7.0.1
Type dependency

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

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
  • βœ… dependency-ci Dependencies checked Details,- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes 7.1 β€œUniversitas litterarum”

Humboldt University of Berlin coat of arms

Autoprefixer 7.1 brings unicode-bidi support, -webkit-appearance to Edge and fix intrinsic widths prefixes in Grid Layout.

unicode-bidi

Autoprefixer 7.1 will add prefixes for isolate, plaintext and isolate-override values in unicode-bidi:

.foo {
  unicode-bidi: -webkit-isolate;
  unicode-bidi: isolate;
}

Edge and -webkit-appearance

Prefixes sometime could be very strange. Edge started to support appearance property with a prefix. But because of many only-for-Safari websites it supports -webkit-appearance instead of -ms-appearance.

Autoprefixer 7.1 knows it and will generate -webkit-appearance even if you set only "last 1 Edge version" in browserslist config.

Intrinsic Widths

min-content, stretch and other Intrinsic sizes was fixed in grid-template-columns and other Grid Layout properties.

.foo {
  grid-template-columns: minmax(100px, -webkit-min-content);
  grid-template-columns: minmax(100px, min-content);
}

Browserslist in info()

By accident Browserslist 1 loaded config from current working dir if file path was missed. In Browserslist 2 we fixed it and now you must specify path to file in explicit way.

It is not a problem for Autoprefixer user, because Autoprefixer takes CSS file path from PostCSS.
But autoprefixer.info() stopped to load conifg in 7.0. In 7.1 we added from option to info().

Set the path to your CSS file and info() will show what prefixes and why it will added to this CSS file:

autoprefixer.info({ from: './scr/app.css' })
//=> Browsers:
//     Chrome: 58
//
//   These browsers account for 1.68% of all users globally
//
//   Selectors:
//     :fullscreen: webkit
//   …
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.25.0 of babel-core just got published.

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

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

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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 babel-runtime is breaking the build 🚨

Version 6.25.0 of babel-runtime just got published.

Branch Build failing 🚨
Dependency babel-runtime
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-runtime 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 postcss-loader is breaking the build 🚨

Version 2.0.5 of postcss-loader just got published.

Branch Build failing 🚨
Dependency postcss-loader
Current Version 2.0.4
Type dependency

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

postcss-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
  • βœ… dependency-ci Dependencies checked Details,- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v2.0.5

Bug Fixes

Commits

The new version differs by 2 commits0.

  • 12c19b9 chore(release): 2.0.5
  • dca52a9 fix: regression with options.plugins {Function} (webpack.config.js) (#229)

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 file-loader is breaking the build 🚨

Version 0.11.2 of file-loader just got published.

Branch Build failing 🚨
Dependency file-loader
Current Version 0.11.1
Type dependency

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

file-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 🌴

hot-update files not found

When I use quik -w index.js and make changes to my components (eg. ./MyComponent.js or ./components/Test.js (imported from ./Mycomponent.js)), I get the following error:

<-- GET /189a6a414e86fb2b35b8.hot-update.json
  --> GET /189a6a414e86fb2b35b8.hot-update.json 200 1ms 36b
  <-- GET /0.189a6a414e86fb2b35b8.hot-update.js
  xxx GET /0.189a6a414e86fb2b35b8.hot-update.js 500 1ms -

  Error: File not found: /Users/jesthoge/Desktop/prototype/0.189a6a414e86fb2b35b8.hot-update.js
      at /usr/local/lib/node_modules/quik/src/configure.js:24:28
      at FSReqWrap.cb [as oncomplete] (fs.js:216:19)

Tested with node version 5.0.0, 5.2.0 and 5.3.0.

Update: Seems to be working if I pull the repo and run bin/quik.js. Is the npm version out of date?

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

Version 2.3.0 of eslint-plugin-import just got published.

Branch Build failing 🚨
Dependency eslint-plugin-import
Current Version 2.2.0
Type devDependency

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

As eslint-plugin-import 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 46 commits.

  • b79e083 Merge pull request #837 from benmosher/release-2.3.0
  • 74425a2 changelog update for 2.3.0
  • 1377f55 bump v2.3.0
  • 2efc41a fix null pointer exception (#717) (#797)
  • 0fb592e Add support to specify the package.json (#685)
  • 2cc9768 Add test for flow type export (#835)
  • bd0e5e3 Merge pull request #821 from smably/patch-1
  • 412e518 Clarify docs for glob arrays
  • 106740f chore(package): update typescript-eslint-parser to version 2.1.0 (#790)
  • 6288cf9 chore(package): update babel-register to version 6.24.1 (#796)
  • 2e9eea6 newline-after-import test syntax fails
  • c9f10e8 extensions test fixes, attempt 2
  • 861765f fix babel syntax errors in extensions tests
  • 82f796c chore(package): update cross-env to version 4.0.0 (#783)
  • 98e7048 Merge pull request #757 from gmathieu/fix-default-keyword

There are 46 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 css-loader is breaking the build 🚨

Version 0.28.3 of css-loader just got published.

Branch Build failing 🚨
Dependency css-loader
Current Version 0.28.2
Type dependency

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

css-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 react is breaking the build 🚨

Version 15.6.1 of react just got published.

Branch Build failing 🚨
Dependency react
Current Version 15.6.0
Type dependency

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

react 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 koa is breaking the build 🚨

Version 2.3.0 of koa just got published.

Branch Build failing 🚨
Dependency koa
Current Version 2.2.0
Type dependency

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

koa 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 30 commits.

  • aaac09a 2.3.0
  • 327b65c Use node 7+ WHATWG parser for hostname, fixes #1002 (#1004)
  • 0125878 added setters for header and headers, fixes #991
  • f6f1ab7 lint: commit --fix
  • 4b41a8b update gitignore, added package-lock
  • 41f8776 test: run ci on node 7,8 (#992)
  • beec26e docs: A middleware is always responsible for calling downstream (#978)
  • 0a7856c docs: Add note about overwriting charset in response.type (#993)
  • 7941fb5 grammar (#994)
  • 08eb1a2 docs: apply Date.now() to all docs (#988)
  • 302814e docs: Fix minor nitpick in documentation (#987)
  • bfce580 Update Readme.md (#985)
  • d394724 test: Use Jest (#981)
  • 13c7ca6 res.type=: remove no-op code (#980)
  • 9248660 test: fix spelling error (#972)

There are 30 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 eslint-plugin-ava is breaking the build 🚨

Version 4.2.1 of eslint-plugin-ava just got published.

Branch Build failing 🚨
Dependency eslint-plugin-ava
Current Version 4.2.0
Type devDependency

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

As eslint-plugin-ava 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 5 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 opn is breaking the build 🚨

Version 5.1.0 of opn just got published.

Branch Build failing 🚨
Dependency opn
Current Version 5.0.0
Type dependency

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

opn 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 🌴

Errors starting quik

$ quik
/Users/dmitrizaitsev/npm-global/lib/node_modules/quik/src/configure.js:30
                ...config.plugins,
                ^^^

SyntaxError: Unexpected token ...
    at exports.runInThisContext (vm.js:53:16)
    at Module._compile (module.js:414:25)
    at Object.Module._extensions..js (module.js:442:10)
    at Module.load (module.js:356:32)
    at Function.Module._load (module.js:311:12)
    at Module.require (module.js:366:17)
    at require (module.js:385:17)
    at Object.<anonymous> (/Users/dmitrizaitsev/npm-global/lib/node_modules/quik/src/bundler.js:3:19)
    at Module._compile (module.js:435:26)
    at Object.Module._extensions..js (module.js:442:10)

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

Version 4.1.2 of eslint-plugin-babel just got published.

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

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

As eslint-plugin-babel 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v4.1.2

Bug Fix

babel/semi: doesn't fail when using for await (let something of {}). Includes class properties

Commits

The new version differs by 2 commits.

  • 1eab147 4.1.2
  • 9468524 Modifying semi rule to support for await (#126)

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 🌴

Future plans

I really love this! It ran my redux demo (https://github.com/flipjs/starting-redux) with no issues!

I hope in the future releases, apart from what you listed, could you also support using react-router and redux-simple-router, then we can also prototype a complete single-page-applications.

Super heavy packaging

Just doing

$ cd template
$ quik

I see on the network tab the index.js is 2.2MB

screen shot 2017-04-20 at 15 41 49

Am I missing something?

SyntaxError: Invalid or unexpected token

i installed quik as global and it was working fine suddenly it stopped working and showing this error

/usr/lib/node_modules/quik/node_modules/lodash.map/index.js:1
(function (exports, require, module, __filename, __dirname) { οΏ½οΏ½οΏ½
^
SyntaxError: Invalid or unexpected token
at createScript (vm.js:53:10)
at Object.runInThisContext (vm.js:95:10)
at Module._compile (module.js:543:28)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (/usr/lib/node_modules/quik/node_modules/cheerio/lib/api/forms.js:7:12)

Remove default packages?

Default packages seems a bit redundant now that npm-install-loader has been added, don't you think?

Production bundle size huge

Give the following impressive application:

File index.html:

<html>
  <body>
    <div id="app"></div>
    <script src="index.js"></script>
  </body>
</html>

File index.js:

import React from 'react';
import ReactDOM from 'react-dom';

const App = () => <h1>Hello quik!</h1>;
ReactDOM.render(<App/>, document.getElementById('app'));

If I execute quik --html index.html --output out.html I get a file out.html with file-size 1781349.

If I execute quik --html index.html --output out.html --production I get a file out.html with file-size 2310640.

Why is production build bigger?

Why are both builds so big?!

Module build failed: ReferenceError: Unknown plugin "transform-runtime" specified in "base" at 0

Hey there, I'm trying out quik this morning and absolutely love the concept. However, I'm not able to get it running. I've installed quik and then added a index.js file to a directory and ran the quik command and receive the following error:

Module build failed: ReferenceError: Unknown plugin "transform-runtime" specified in "base" at 0, attempted to resolve relative to "/Users/andrewdelprete/Work/Code Testing/quik-test"

Do I need to install npm transform-runtime -g perhaps? Thank you!

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

Version 15.6.1 of react-dom just got published.

Branch Build failing 🚨
Dependency react-dom
Current Version 15.6.0
Type dependency

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

react-dom 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error 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 eventsource is breaking the build 🚨

Version 1.0.5 of eventsource just got published.

Branch Build failing 🚨
Dependency eventsource
Current Version 1.0.4
Type devDependency

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

As eventsource 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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 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-loader is breaking the build 🚨

Version 7.1.0 of babel-loader just got published.

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

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

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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes 7.1.0

πŸš€ New Feature

  • Update to support webpack 3 (#471) (Joe Lencioni)
  • look for babel options in package.json and .babelrc.js (babel 7) (#465) (Thomas Sileghem)
  • Watch configuration files. (#460) (Evilebot Tnawi)
    You can now change the babel config while webpack watch or dev-server is running and webpack will correctly recompile all files with babel.

πŸ› Bug Fix

  • Only base cache identifier on babel options from package.json (#468) (Daniel Tschinder)

πŸ“ Documentation

  • Remove outdated examples. (Daniel Tschinder)

🏠 Internal

  • update eslint-config-babel to version 7.0.0 (#469) (greenkeeper[bot])
  • update lint-staged to version 4.0.0 (#470) (greenkeeper[bot])
  • Add prettier eslint plugin (#466) (Daniel Tschinder)
  • Add node 8 to test matrix (#467) (Daniel Tschinder)
  • Upgrade find-cache-dir to 1.0 and cross-env to 5.0 (#457) (Daniel Tschinder)
Commits

The new version differs by 13 commits.

  • d249119 7.1.0
  • ea9b4d4 Update yarn.lock
  • 7986787 chore(package): update eslint-config-babel to version 7.0.0 (#469)
  • ee40748 chore(package): update lint-staged to version 4.0.0 (#470)
  • 66784e4 Update to webpack 3 (#471)
  • 8544ffa Only base cache identifier on babel options from pkg.json (#468)
  • ea2eafa Add prettier eslint plugin (#466)
  • 4548169 Add node 8 to test matrix (#467)
  • d8b73c0 fix(resolve-rc): look for babel in package.json and .babelrc.js (#465)
  • 8d96c1f Remove outdated examples.
  • 91f2658 Fixed: watch configuration files. (#460)
  • de2d3f3 Upgrade dependencies
  • 37e63e3 Upgrade find-cache-dir to 1.0 and cross-env to 5.0 (#457)

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 sass-loader is breaking the build 🚨

Version 6.0.6 of sass-loader just got published.

Branch Build failing 🚨
Dependency sass-loader
Current Version 6.0.5
Type dependency

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

sass-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
  • βœ… dependency-ci Dependencies checked Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 9 commits.

  • a1ae204 chore: Update changelog for 6.0.6
  • aed60eb chore(release): 6.0.6
  • 85d7772 chore: Adds release script
  • 43199f1 chore: Reformat changelog for standard-version
  • 5daa32b chore(package): Adds contrib standard release tooling
  • 0511c25 chore: build and package updates to allow use of webpack 3 (#475)
  • 0d6d66d refactor: remove this.cacheable (#473)
  • 876876a docs(readme): Fixes typo in loader description (#472)
  • c27063c chore(package): update dependencies (#470)

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 sass-loader is breaking the build 🚨

Version 6.0.5 of sass-loader just got published.

Branch Build failing 🚨
Dependency sass-loader
Current Version 6.0.4
Type dependency

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

sass-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
  • βœ… dependency-ci Dependencies checked Details,- ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v6.0.5
  • fix: importing file directly from scoped npm package #450
Commits

The new version differs by 4 commits0.

  • c61eaee Merge pull request #453 from webpack-contrib/Release/6.0.5
  • fe4af44 chore(release): 6.0.5
  • cbc0794 chore: Update changelog
  • 5d06e9d fix: importing file directly from scoped npm package (#450)

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 🌴

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.