Closed cowboyd closed 9 years ago
Hi and thanks for your issue!
You can install the package using bower if that is your thing instead of npm:
➜ test git:(master) ✗ bower i omniscientjs/immstruct
bower immstruct#* not-cached git://github.com/omniscientjs/immstruct.git#*
bower immstruct#* resolve git://github.com/omniscientjs/immstruct.git#*
bower immstruct#* download https://github.com/omniscientjs/immstruct/archive/v1.4.1.tar.gz
bower immstruct#* extract archive.tar.gz
bower immstruct#* invalid-meta immstruct is missing "main" entry in bower.json
bower immstruct#* invalid-meta immstruct is missing "ignore" entry in bower.json
bower immstruct#* resolved git://github.com/omniscientjs/immstruct.git#1.4.1
bower immstruct#~1.4.1 install immstruct#1.4.1
immstruct#1.4.1 bower_components/immstruct
➜ test git:(master) ✗ cat bower_components/immstruct/dist/immstruct.min.js | head -c100
/**
* immstruct v1.4.1
* Authors: Mikael Brevik, @torgeir
***************************************/
!% ➜ t2 git:(master) ✗
Version tracking could be somewhat harder, though, as we don't have a bower.json, but you could use github tags to do it?
We try to not have too much complexity in distribution, so we limit the dist files to automatic cdn and through npm (which I think is probably going to be the industry standard and sort of already is).
gotcha, I'm mainly thinking about making sure the dependencies are correctly met. I'm using immutable from bower, and immstruct from npm because the immutable in npm only contains the commonjs module.
It would be nice if immstruct were installable as a bower component.