Since we use Lerna for managing our monorepo, we benefit by keeping majority of our common devDependencies in the root package.json.

Packages like Babel, ESLint, etc are all listed as devDependencies. Also also all site related packages (like metalsmith) are listed in root package.json too.

But there are also some, which are not common across all packages:

• http-server (examples only)
• jsdom (only frint-test-utils need it, iirc)
• live-server (examples only)
• react (only frint-react and frint-react-server should need it)
• react-addons-test-utils (only frint-react and frint-react-server should need it)
• react-dom (only frint-react and frint-react-server should need it)
• rxjs

They should either be moved to appropriate packages as their own devDependencies, or removed altogether (because examples have their own package.json files now).

Currently

Right now we can do:

const Todo = createModel({...});

const todo = new Todo({ title: 'My First Todo' });
const title = todo.get('title'); // `My First Todo`

Expected feature

It would be beneficial for form management, if we can observe Model values too:

const title$ = todo.get$('title');

title$.subscribe(x => console.log(x));

todo.set('title', 'Updated title'); // prints out title in console

Benefit

Then for handling forms in component, we could do something like this with frint-react's observe:

import React from 'react';
import { observe, streamProps } from 'frint-react';

const FormComponent = React.createClass({...});

export default observe(function () {
  const todo = new Todo({ title: 'My todo' });

  return streamProps()
    .set(
      todo.get$(),
      todoAttributes => ({ todo: todoAttributes })
    )
    .get$();
})(FormComponent);

App names are very frequently used, and an integral part of inter-app communication.

Instead of doing:

app.getOption('name');

It's worth giving it a dedicated method:

app.getName();

Since name in options is a required key.

To be compatible with latest Webpack in root package.json.

Upgrade ./examples/multiple-widgets with latest Frint v1.0

Version 9.12.0 of jsdom just got published.

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

As jsdom 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 💪

Your Greenkeeper Bot 🌴

Version 4.1.0 of alex just got published.

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

As alex 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 💪

Your Greenkeeper Bot 🌴

Upgrade ./examples/counter with latest Frint v1.0

Currently

The root application is required to load and inject itself into the window global before any other child application can register. This prevents us from adding the async attribute to the script, which allows us to load multiple scripts in parallel.

// In index.html
<script src="https://example.com/assets/root.js"></script>
<script src="https://example.com/assets/childApp.js"></script>

// In root.js
window.app = new App();
render(window.app, containerElement);

// In childApp.js
window.app.registerApp(ChildApp, {
  regions: ['main'],
});

Proposed

The proposed changes would allow to load root and child apps asynchronously, but in a way that execution order is not guaranteed. Doing this would increase the time to first paint and would prevent the script from blocking any other script parsing and/or layout render.

We achieve this by injecting a placeholder array for the root app on each child app, when it's not currently available. When the root app is loaded, we replace the placeholder array with the root app. By adding a push method to the Application API, we can emulate the array's own. This way, child apps don't need to be aware if they're pushing to an array or to the actual root application.

Prior Art: http://googlecode.blogspot.nl/2009/12/google-analytics-launches-asynchronous.html

// In index.html
// Note the addition of the async attribute
<script src="https://example.com/assets/rootApp.js" async></script>
<script src="https://example.com/assets/childApp.js" async></script>

// In root.js
const rootApp = new RootApp();
window.app.forEach(app => rootApp.push(app));
window.app = rootApp;
render(rootApp, containerElement);

// In childApp.js
window.app || window.app = [];
window.app.push({
  app: ChildApp,
  regions: ['main'],
});

To be done:

• Add the push method to the App component, this should internally call the registerApp method.
• Remove the dependency on any window global in library code, see Region.js See Fahad's comment
• Create test scenarios where child apps run before the root app.

Version 6.4.0 of babel-loader just got published.

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

As babel-loader 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 💪

Your Greenkeeper Bot 🌴

Version 2.5.0 of webpack just got published.

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

As webpack 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 💪

Your Greenkeeper Bot 🌴

Version 3.4.0 of mocha just got published.

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

As mocha 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 💪

Your Greenkeeper Bot 🌴

Right now, app.render() returns the Component class, so the method name feels misleading.

Refs #80

Create a new package in this repo called frint-preset-react, and it will install these dependencies:

• frint
• frint-model
• frint-store
• frint-react

Besides only bringing the dependencies via npm install, we can provide webpack.config.js for generating dist files (which can even be pushed to npm, and later made available via unpkg CDN). IT would generate two files:

• dist/frint-preset-react.js (only frint-* libraries)
• dist/frint-preset-react.full.js (RxJS, Lodash, React + frint-* libraries)

I am undecided about another preset called frint-preset-travix, whether it should be in this repo or not.

This preset would extend frint-preset-react, and also add:

• frint-compat

Currently shows a dark color, which doesn't really go with rest of the site:

Version 2.8.8 of uglify-js just got published.

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

As uglify-js 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 💪

Your Greenkeeper Bot 🌴

Because createClass doesn't exist in frint: https://github.com/Travix-International/frint/blob/master/packages/frint-compat/src/createService.js#L5

Same in createFactory.

Will be nice to have an access to components props (which is passed by parent) in observe. This feature can allow to perform some actions, get some stuff from "store" according to passed value, or even simply wrap up third-party component without creating the new one.
This proposal is inspired by react-redux package which allow to do same things.

We've used in our application 'streamProps' for streaming props, but it's not mapping the updated store to props and as a result, in the widget we have outdated old props despite the actions and reducers work in correct way and state is correct. Here's the usage of the function:
return streamProps({}) .set( store.getState$(), state => state.carShow )

Version 3.17.1 of eslint just got published.

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

As 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 💪

Your Greenkeeper Bot 🌴

Show developers how Redux can be used with Frint.

https://redux.js.org

Create an example demonstrating css-modules.

Version 10.3.2 of nyc just got published.

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

As nyc 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 💪

Your Greenkeeper Bot 🌴

See if ReactRouter can be implemented at all with Frint. I am mainly worried about context being hijacked.

https://github.com/ReactTraining/react-router

Sometimes it is like, from one Widget, I would like to know if another Widget is available or not, and then do something.

app.waitUntilMounted('anotherAppsName', 5000)
  .then(function (anotherAppInstance) {
    // found `anotherApp` within 5 seconds of waiting
  })
  .catch(function () {
    // 5 seconds waiting period has passed
  });

Can possibly be done as an Observable, instead of Promise to allow it to be cancellable on demand.

At the moment, any App instance can register other Apps:

myAppInstance.registerApp(SomeOtherApp);

Opt-in API example

We primarily want only Root Apps to be able to register other apps. We can do it with an API like this:

import { createApp } from 'frint';

const RootApp = createApp({
  registerable: true, // by default, it will be `false`
});

OR, we can possibly go ahead with a decorator-like API:

import { createApp, makeItRegisterable } from 'frint';

const RootApp = createApp({});

export default makeItRegisterable()(RootApp);

Doing so means, only those Apps we explicitly want to be able to register other Apps, will allow methods like .registerApp().

Version 2.12.0 of coveralls just got published.

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 💪

Your Greenkeeper Bot 🌴

Should we add preinstall script to main package.json for easy installing node modules for all packages before installing root modules?

Add a search bar to the documentation to be able to search.
An example can be the search bar used in Gitbook, for example here: https://codiechanel.gitbooks.io/gitbook-demo/content/

And also see how we can keep things backwards compatible with React v0.14.

Instead of developers explicitly requesting for a particular Service of Factory, let them request for the instance just by their name (without having to know whether it is a Service or a Factory).

Example API (doesn't mean it will be the final API):

import FooService from './services/Foo';
import BarFactory from './factories/Bar';

const App = createApp({
  providers: {
    foo: FooService,
    bar: BarFactory
  }
});

const app = new App();

const fooService = app.get('foo'); // returns service
const barFactory = app.get('bar'); // returns factory

// same way, mapToProps() can also have `providers` key:
const ContainerComponent = mapToProps({
  providers: {
    foo: 'foo',
    bar: 'bar',
  }
})(RootComponent);

Version 6.24.0 of babel-core just got published.

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

As babel-core 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 💪

Your Greenkeeper Bot 🌴

Version 6.24.0 of babel-register just got published.

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

As babel-register 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 💪

Your Greenkeeper Bot 🌴

Region is a feature mainly found in frint-react package. So frint package itself doesn't need to have it baked in.

Version 6.20.0 of babel-core just got published.

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

As babel-core 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 💪

Your Greenkeeper Bot 🌴

If mapToProps is called for only binding self state, it doesn't really need to bind data for shared states too unless requested.

For example, if this is the implementation of a Root component:

mapToProps({
  state(state) {
    return { 
      counter: state.counter.value 
    };
  }
})(RootComponent);

then, we don't need to listen to shared states from other App instances.

Implement a /packages page in the site, that lists all npm packages with the keyword frint.

Inspiration can be taken from: http://gulpjs.com/plugins/

NPM search can be made against https://npmsearch.com/

Docs for REST API usage: https://github.com/nodesource/npmsearch#api

Because otherwise the dependency versions in frint-preset-travix/package.json won't be pinned like we want, to control what goes to production for Travix.

Create a FrintJS example following http://todomvc.com/, which is the community standard for recreating the same application with same behaviour, using various frameworks.

Drop usage of http-server and remove it from root package.json: https://github.com/Travix-International/frint/blob/02266ff86d8034f07db3ad48836966ee2d648176/package.json#L63

And use live-server instead.

It would be nice to add smth like onLoad event for app when it's just being loaded to page (when FRINT_INIT action is dispatched, not when beforeMount is called)

we have now a problem with subscribing for message broker.

Version 3.8.4 of js-yaml just got published.

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

As js-yaml 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 💪

Your Greenkeeper Bot 🌴

Version 5.3.1 of rxjs just got published.

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

As rxjs 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 💪

Your Greenkeeper Bot 🌴

Likely a bug, or I am mistaken. But needs to be confirmed.

To reproduce

• Create a Store with:
  • Combined reducers
  • Where one reducer has default state at function level

const INITIAL_STATE = {
  foo: 'bar'
};

function myReducer(state = INITIAL_STATE, action) {
  // ...
}

• Then try instantiating the Store with no initialState key, with data that one of the reducer expects:

const Store = createStore({
  reducer: combinedReducer
});

const store = new Store();

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

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 💪

Your Greenkeeper Bot 🌴

Right now, we can render multiple Widgets inside a Region. It would be nice to control the ordering of the Widgets too. Right now, there is no clear way of predicting it.