Quill: Re-add built distribution for v1.0

[murran]

I saw previous discussion reg. issue #144

However it seems like the practice of including a build distribution in releases disappeared with version 1.0. Are you planning on re-adding it? Its helpful for bower workflows, etc

Thanks for quill btw, it seems awesome!

[alexkrolick]

This looks like a temporary issue that was fixed in 1.0.2.

[murran]

Not that I can see, would you mind linking to the relevant files?

[alexkrolick]

Download the released tar archive -- it has the minified versions. That is what NPM will give you as well.

@murran Latest release: https://github.com/quilljs/quill/releases/tag/v1.0.3

[murran]

Alright, thanks @alexkrolick! Just out of curiosity, why is it part of the npm package but not the bower one?

[sumitkm]

Can we please have the dist folder as a part of the bower installation also... pretty please!

[jhchen]

Git is for source code, not built distributions. Tools that do support built distributions like NPM, Github releases, and Quill's CDN have Quill's built files, as others have already stated.

[murran]

For anyone having the same issue as me, I realised I could get bower to supply the distribution by using bower install quill=https://github.com/quilljs/quill/releases/download/v1.0.3/quill.tar.gz --save

It's not as pretty as usual bower entries, but works :)

[sumitkm]

:100: @murran Brilliant, that definitely beats maintaining a fork with the dist folder (as I was planning to do)!!!

[dmonad]

@jhchen I agree with you, but that is very unsatisfying to everyone who is using bower instead of npm. Maybe it makes sense to add @murran's workaround to the documentation. This would be very helpful to others facing the same problem.

I create commits that are not tracked by a branch for my releases. This is a great solution for me, as dist files don't bother me when merging, etc. For example:

% publish a new version
$ git checkout --detach
$ git add ./dist/* -f
$ git commit -am "dist files for v${p.version}"
$ git tag v${p.version}
$ git push origin v${p.version} % push the tag
$ git checkout master

I'd be happy to create a pull request with an updated publishing script.

[alexkrolick]

Does bower use a different registry than NPM? It seems like the solution is to
either point Bower at a tagged release (eg github.com/quilljs/quill#1.0.3
would resolve in the NPM package manager), or to publish a proper bower
version.

[sumitkm]

@alexkrolick yes, it does use a different registry. I am no expert, but I just looked up another library I use (require js) and the bower package for that doesn't point to the require code repo, instead it points to a repo that only has the release version of require.js.
I can understand @jhchen 's reluctance to maintain it that way, does seem like a bit of hack.

So @murran 's solution is a nice middle ground (for me atleast) :-)

[jziggas]

Just giving another anecdote. Tried to upgrade (bower) Quill in our project after probably 12+ months of being on 0.2.x. I expected some breaking changes but not finding the dist folder at all was a little disorienting! Trying to figure out what happened was not easy either since nothing was mentioned in the readme or quickstart guide. Trying to find a way to get our Gulpfile to build everything would have been a pain too. It's nice to at least see the bower workaround provided by @murran, thanks.