Important: This documentation covers Yarn 1 (Classic).
For Yarn 2+ docs and migration guide, see yarnpkg.com.

Package detail

ran-boilerplate

Sly77752MIT0.8.3TypeScript support: included

React . Apollo (GraphQL) . Next.js Toolkit

next.js, react, graphql, boilerplate, apollo, styled-components, ran, run, toolkit

readme

RAN

RAN : React . GraphQL . Next.js Toolkit

Backers on Open Collective Sponsors on Open Collective Greenkeeper badge All Contributors Join the chat at https://gitter.im/ran-boilerplate/Lobby Build Status license
Code Climate Known Vulnerabilities npm styled with prettier GitHub stars

Features

  • Hot-Reload Ready for Dev

  • Next Generation JavaScript (ES6)

  • Offline Ready (Experimental!)

  • Next Generation CSS (CSS-in-JS)

  • Create New Page in a Second (with CLI)

  • SEO-Ready

  • Performance-first

  • Production Deployment Ready for Now, Digital Ocean and Heroku

  • Prettier and ESLint integrated

How to use

  • Firstly, clone the repo with this command.
git clone --depth=1 https://github.com/Sly777/ran.git RAN
cd RAN
yarn && yarn setup
  • If you are not using Yarn, just run npm install && npm run setup instead of yarn && yarn setup
  • After everything is finished, run yarn dev (or npm run dev)

And that's all!

Start coding on browser! (via Glitch)

Just click the button and then start to work with RAN!

Remix on Glitch

Clean Setup (without example pages & components)

git clone --depth=1 https://github.com/Sly777/ran.git RAN
cd RAN
yarn && yarn setup:clean

Beta Version (Unstable)

Also, there is a beta version for new features & fixes that we are testing before release. To access beta;

git clone --depth=1 -b beta https://github.com/Sly777/ran.git RAN_beta
cd RAN_beta
yarn && yarn setup

It can be unstable, so that's why please use stable version if you are working on the project that is in production.

Example

Click here to see example project to understand how RAN! works on production. I used graph.cool service for GraphQL and now for hosting in the example.

Commands

Best feature of RAN! is CL commands. You can just run one command to create page with route! Click here to see details how It works on RAN!.

YAY YAYY

Documentation

Click here to see all details of RAN!

FAQ

Click here for FAQ of RAN! If it doesn't solve your problem, feel free to open an issue on GitHub!

License

This project is licensed under the MIT license, Copyright (c) 2017 Ilker Guller. For more information see LICENSE.md.

Contributing

Please read Contributing doc for details on our code of conduct, and the process for submitting pull requests.

Versioning

RAN! is using SemVer for versioning. For the versions available, see the tags on this repository.

Author

Contributors

Thanks goes to these wonderful people:

Backers

Thank you to all our backers! [Become a backer]

Sponsors

Thank you to all our sponsors! (please ask your company to also support this open source project by becoming a sponsor)

changelog

0.11.1 / 2017-01-22

  • Forcibly close the I/O stream after a timeout if the peer does not respond after calling close()

0.11.0 / 2016-02-24

  • Introduce a net option to the Client class for setting things like, say, servername

0.10.0 / 2015-07-08

  • Add the standard code and reason parameters to the close method

0.9.4 / 2015-03-08

  • Don't send input to the driver before start() is called

0.9.3 / 2015-02-19

  • Make sure the TCP socket is not left open when closing the connection

0.9.2 / 2014-12-21

  • Only emit error once, and don't emit it after close

0.9.1 / 2014-12-18

  • Check that all options to the WebSocket constructor are recognized

0.9.0 / 2014-12-13

  • Allow protocol extensions to be passed into websocket-extensions

0.8.1 / 2014-11-12

  • Send the correct hostname when upgrading a connection to TLS

0.8.0 / 2014-11-08

  • Support connections via HTTP proxies
  • Close the connection cleanly if we're still waiting for a handshake response

0.7.3 / 2014-10-04

  • Allow sockets to be closed when they are in any state other than CLOSED

0.7.2 / 2013-12-29

  • Make sure the close event is emitted by clients on Node v0.10

0.7.1 / 2013-12-03

  • Support the maxLength websocket-driver option
  • Make the client emit error events on network errors

0.7.0 / 2013-09-09

  • Allow the server to send custom headers with EventSource responses

0.6.1 / 2013-07-05

  • Add ca option to the client for specifying certificate authorities
  • Start the server driver asynchronously so that onopen handlers can be added

0.6.0 / 2013-05-12

  • Add support for custom headers

0.5.0 / 2013-05-05

  • Extract the protocol handlers into the websocket-driver library
  • Support the Node streaming API

0.4.4 / 2013-02-14

  • Emit the close event if TCP is closed before CLOSE frame is acked

0.4.3 / 2012-07-09

  • Add Connection: close to EventSource response
  • Handle situations where request.socket is undefined

0.4.2 / 2012-04-06

  • Add WebSocket error code 1011.
  • Handle URLs with no path correctly by sending GET /

0.4.1 / 2012-02-26

  • Treat anything other than a Buffer as a string when calling send()

0.4.0 / 2012-02-13

  • Add ping() method to server-side WebSocket and EventSource
  • Buffer send() calls until the draft-76 handshake is complete
  • Fix HTTPS problems on Node 0.7

0.3.1 / 2012-01-16

  • Call setNoDelay(true) on net.Socket objects to reduce latency

0.3.0 / 2012-01-13

  • Add support for EventSource connections

0.2.0 / 2011-12-21

  • Add support for Sec-WebSocket-Protocol negotiation
  • Support hixie-76 close frames and 75/76 ignored segments
  • Improve performance of HyBi parsing/framing functions
  • Decouple parsers from TCP and reduce write volume

0.1.2 / 2011-12-05

  • Detect closed sockets on the server side when TCP connection breaks
  • Make hixie-76 sockets work through HAProxy

0.1.1 / 2011-11-30

  • Fix addEventListener() interface methods

0.1.0 / 2011-11-27

  • Initial release, based on WebSocket components from Faye