Using superagent with bower
See original GitHub issueHey I’m trying to use v1.8.0 with bower. After installing it with bower I don’t know which js file I am supposed to include in my project. Before in older versions there was the file /bower_components/superagent/superagent.min.js
but that doesn’t exist no more. Please advise.
Issue Analytics
- State:
- Created 8 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Using superagent with bower · Issue #936 - GitHub
Hey I'm trying to use v1.8.0 with bower. After installing it with bower I don't know which js file I am supposed to...
Read more >angular-superagent on Bower - Libraries.io
Angular wrapper for Superagent - a JavaScript package on Bower ... Include release/angular-superagent.js and register the ngSuperagent module in your app.
Read more >How do I use SuperAgent in a simple MVC 5 app?
I am trying to use SuperAgent.js in a simple HTML page in a MVC 5 app I ... I was able to create...
Read more >org.webjars.bower:superagent vulnerabilities - Snyk
Known vulnerabilities in the org.webjars.bower:superagent package. This does not include vulnerabilities belonging to this package's dependencies.
Read more >bright-superagent - npm
SuperAgent is a small progressive client-side and Node.js HTTP request library, sporting many high-level HTTP client features. View the docs.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also in general with the releases here, where are the final production files? I would expect a
superagent.js
and asuperagent.min.js
file included in the artifacts in the github releases. But alas all I see is source code zips and tars. Seriously?git repository shouldn’t contain derived files, especially when they’re unmergeable. I’d prefer not to add such files just because Bower is confuses source code with a built product.
My suggestions:
Consider abandoning Bower. NPM 3 has a flat directory structure. Yarn has
--flat
switch that enforces Bower-like version resolution.If you have to use Bower, use build tools like Gulp and Webpack that will build and minify superagent’s source for you.
If you really have to use Bower and can’t have a build step, fork this repository and add and maintain the derived files yourself.