These are chat archives for bespokejs/bespoke

30th
Sep 2015
Dan Allen
@mojavelinux
Sep 30 2015 05:54
@markdalgleish I noticed the version in the comment at the top of the files in the dist folder in bespoke-core is incorrect. It says that it is version 1.0.0, but it should be 1.1.0. https://github.com/bespokejs/bespoke/blob/master/dist/bespoke.js
Mark Dalgleish
@markdalgleish
Sep 30 2015 07:28
Times have changed a bit since Bespoke started
That raises a question I've had in the back of my mind
No more `
Is it time to go all in on npm, drop Bower and browser globals?
Mark Dalgleish
@markdalgleish
Sep 30 2015 08:16
Bah, Gitter mobile messed up my messages
I'll try again...
That raises a question I've had in the back of my mind
Times have changed a bit since Bespoke started
Is it time to go all in on npm, drop Bower and browser globals?
No more dist directory with browserified output, no more pointless copyright header
That's probably the only thing that really shows the project's age
@mojavelinux the fact that you've had pull requests with merge conflicts due to the dist directory is probably the main reason I'd be keen to go CommonJS only
you just don't have these issues when you only care about npm
Dan Allen
@mojavelinux
Sep 30 2015 19:21
I personally have no attachment to Bower. I'll admit I'm used to loading the libraries from dist in the demo, but that setup can easily be reworked. But my approach to using Bespoke externally is always through gulp / npm.
As far as maintenance is concerned, I totally agree that dealing with dist is a pain. I'm constantly having to check that in and even deal with merge conflicts between my own branches.