Hello dear crossbar.io team,
I’ve got a question regarding bower and a remark to npm in adjunct to this.
Are there any plans in dropping the bower support? I mean, why not publishing the autobahn-js-built package to npm? Bower isn’t used for most front-end related projects anymore. I certainly do not want to add it as a dependency in our projects. I would not mind giving a helping hand on the publishing to NPM part if that would helpful?
And in regard to npm itself is that if you do plan to publish to npm, I would suggest using scoped packages. That would identify crossbar and autobahn in general more. Just like the crossbario/crossbar docker image which is obvious to come from Crossbar.io (if there are no security issues, no-one should be able to push to the crossbario space).
Thanks in advance!
Regards,
Jogchum Koerts.
I would like to bump my questions since it has been almost a month without a response.
Thanks in advance!
···
On Thursday, 1 March 2018 16:54:41 UTC+1, Jogchum Koerts wrote:
Hello dear crossbar.io team,
I’ve got a question regarding bower and a remark to npm in adjunct to this.
Are there any plans in dropping the bower support? I mean, why not publishing the autobahn-js-built package to npm? Bower isn’t used for most front-end related projects anymore. I certainly do not want to add it as a dependency in our projects. I would not mind giving a helping hand on the publishing to NPM part if that would helpful?
And in regard to npm itself is that if you do plan to publish to npm, I would suggest using scoped packages. That would identify crossbar and autobahn in general more. Just like the crossbario/crossbar docker image which is obvious to come from Crossbar.io (if there are no security issues, no-one should be able to push to the crossbario space).
Thanks in advance!
Regards,
Jogchum Koerts.