gaearon

Note:

When this guide is more complete, the plan is to move it into Prepack documentation.
For now I put it out as a gist to gather initial feedback.

A Gentle Introduction to Prepack (Part 1)

If you're building JavaScript apps, you might already be familiar with some tools that compile JavaScript code to equivalent JavaScript code:

• Babel lets you use newer JavaScript language features, and outputs equivalent code that targets older JavaScript engines.

trueadm

const State = React.createState();

function MyComponent(props) {
  return (
    <State
      initialState={() => ({ counter: 0, lastProps: props, divRef: React.createRef() }) }
      deriveState={state => ({ lastProps: props }) }
      shouldUpdate={(state, nextState) => ... }
      didMount={(state, setState) => ... }
      getSnapshotBeforeUpdate={state => ... }

karllhughes

Setup Work

• Make a list of competitive/alternative services: See competitors.md file
• Set up Google News alerts for "side project marketing" and "startup marketing".
• Make list of blogs, subscribe to RSS feeds in Feedbin:
  • Startup marketing blogs
  • Side project blogs
  • Small business marketing blogs
  • Chicago small business/startup bloggers
• Come up with a name and domain name

mosquito

Docker compose as a systemd unit

Create file /etc/systemd/system/[email protected]. SystemD calling binaries using an absolute path. In my case is prefixed by /usr/local/bin, you should use paths specific for your environment.

[Unit]
Description=%i service with docker compose
PartOf=docker.service
After=docker.service

thevangelist

import React from 'react';
import { shallow } from 'enzyme';
import MyComponent from '../src/my-component';

const wrapper = shallow(<MyComponent/>);

describe('(Component) MyComponent', () => {
  it('renders without exploding', () => {
    expect(wrapper).to.have.length(1);
  });

Entalyan

/* DROP STATEMENTS */
DROP TABLE USER_ROLES;
DROP TABLE USER_LOGINS;
DROP TABLE USER_CLAIMS;
DROP TABLE USERS;
DROP SEQUENCE USER_ROLES_SEQ;
DROP SEQUENCE USER_LOGINS_SEQ;
DROP SEQUENCE USER_CLAIMS_SEQ;
DROP SEQUENCE USERS_SEQ;

Entalyan

/* DROP STATEMENTS */
DROP TABLE USERS_USER_ROLES;
DROP TABLE USER_ROLES;
DROP TABLE USER_LOGINS;
DROP TABLE USER_CLAIMS;
DROP TABLE USERS;

/* USERS */
CREATE TABLE USERS
(

idibidiart

Building a Maintainable, Agile Architecture for Realtime, Transactional Apps

A maintainable application architecture requires that the UI only contain the rendering logic and execute queries and mutations against the underlying data model on the server. A maintainable architecture must not contain any logic for composing "app state" on the client as that would necessarily embed business logic in the client. App state should be persisted to the database and the client projection of it should be composed in the mid tier, and refreshed as mutations occur on the server (and after network interruption) for a highly interactive, realtime UX.

With GraphQL we are able to define an easy-to-change application-level data schema on the server that captures the types and relationships in our data, and wiring it to data sources via resolvers that leverage our db's own query language (or data-oriented, uniform service APIs) to resolve client-specified "queries" and "mutations" against the schema.

We use GraphQL to dyn

eyston

const node = Relay.QL`
  query {
    node(id: $channelId) {
      ... on Channel {
        joined
        ${JoinChannelMutation.getFragment('channel')}
      }
    }
  }
`;

istarkov

How to setup atom with nuclide plugins.

You need to install next packages

• hyperclick
• nuclide-diagnostics-store
• nuclide-diagnostics-ui
• nuclide-flow

You need to add .flowconfig