Joscha Rohmann

Hi @wlekin, can you provide some more information about the problem ? An example of how you 're including the file would be great.

What needs to be done here? I would move the jsvalue-built to a seperate grunt task so we could build it for testing but don't build it in the default...

Hi :smile: , > Why we need that? Can't we move that to the jsvalue project? I mean the integration task (the once that currently built the `blocks-source.js` and `blocks-query-data.js`....

I'm currently working on this and stumbled accross a hard-dependencie in the DataSource.js (or precisely [here](https://github.com/astoilkov/jsblocks/blob/e87d5c0eb8070ff5ea88e964a097e3ca1cf8f2d5/src/dataSource/DataSource.js#L327) ). We could: 1. reimplement the missing methods: `size`, `at`, `isEmpty` and `each` 2....

I created a [branch](https://github.com/astoilkov/jsblocks/tree/remove-value) that's resolving this. I mostly removed internal usage of jsvalue apis and just moved a few over to jscore. Namely: ``blocks.toObject``, ``blocks.flatten`` and ``blocks.pairs``. We are...

I can look into building a release. I'm also planning to (or at least I'm think about) make travis build and publish releases (tagged commits on the master branch). At...

I would let travis push the build folder to npm, bower and github (and probably some other destination I missed) via an [deployment script hook](https://docs.travis-ci.com/user/deployment/script/) with the [options](https://docs.travis-ci.com/user/deployment/#Conditional-Releases-with-on%3A) `tags` set...

Hmm okay after thinking and research for a while I've found one major problem I wasn't aware of: bower. Or to be more precise: the fact that bower uses tags...

No stress. I know that situation well. Take your time

We can still support bower. I just need to get a diff of the package.json on the latest master commit and test if the version changed. That's a problem I...