current package.json is:

  "dependencies": {
    "browserify":"*",
    "envify": "^1.2.1",
    "es6-promise": "*",
    "fuzzy": "^0.1.0",
    "gulp": "*",
    "gulp-browserify": "*",
    "gulp-uglify": "*",
    "gulp-util": "*",
    "gulp-concat": "*",
    "gulp-watch": "*",
    "react": "*",
    "react-async": "^2.0.1",
    "moment": "*",
    "tether": "*",
    "react-onclickoutside": "*",
    "reactify": "git://github.com/andreypopp/reactify.git#v0.16.0",
    "reqwest": "*",
    "griddle-react": "0.2.4",
    "griddle-callback": "0.2.0",
    "react-bootstrap": "*",
    "vinyl-source-stream": "*",
    "watchify": "*"
  },

but imo not all these libs are real dependency but only devDependenci (for example: gulp, gulp-uglify, guld-*, watchify etc.)

Is there any plan to update this code to React 15? It seems to have a lot of old stuff in there and needs updating.

15:32:53 client.1 | ERROR in ./~/react-datetime/css/react-datetime.css
15:32:53 client.1 | Module parse failed: /redacted/node_modules/react-datetime/css/react-datetime.css Unexpected token (5:0)

Solved by adding:

config.module.loaders.push(
  {
    test: /\.css$/,
    loader: "style-loader!css-loader"
  }
);

to my webpack config. This is probably a super common set up so maybe worth adding to the README. Happy to do a PR next week.

Hi,
Thanks for doing this, it's really cool! I had seen visualsearch and been meaning to try it for react.rocks.

Date issue:

The IPO column is shown as a year, but the date picker is day level of granularity.

Seems wrong...guess the IPO is really a day, but rounded down to the year? Seems like it'd be more intuitive if the date were displayed.

Hard to tell without the git history 😁

When we select a date , its not very intuitive that we need to press back on the input box to make the date selection effective.
This is a bad user experience and if we have something like a submit button , for date selection pop over , it would be of great help.

Once we select a filter and create a couple more of them , its a common use case that we need to go back and edit the previous filter. Its a bad user experience to remove the tag and create it from scratch.
Rather if we can click on the tag and edit them , that would be a better user experience.

Hi @joshcarr ,

I'm using the minimalist feature of the filter like

<StructuredFilter
    placeholder="Search..."
    options={[
        {category:"Name",type:"text"},
        {category:"Price",type:"number"},
    ]}
/>

and I'm getting the error

Uncaught TypeError: Cannot read property 'slice' of undefined
getStateFromProps 
Tokenizer 
constructComponentWithoutOwner 

Could you please help.

Could you make this available on https://www.npmjs.com?

i am using Material Design in my project, so i don't want to import BS... :(