chromeExtensionAsync | Promise wrapper for the Chrome extension API | Reactive Programming library

by KeithHenry JavaScript Version: v3.3.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | chromeExtensionAsync Summary

chromeExtensionAsync is a JavaScript library typically used in Programming Style, Reactive Programming applications. chromeExtensionAsync has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i chrome-extension-async' or download it from GitHub, npm.

Promise wrapper for the Chrome extension API so that it can be used with async/await rather than callbacks

Support

Quality

Security

License

Reuse

Support

chromeExtensionAsync has a low active ecosystem.

It has 214 star(s) with 32 fork(s). There are 7 watchers for this library.

It had no major release in the last 12 months.

There are 6 open issues and 17 have been closed. On average issues are closed in 107 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of chromeExtensionAsync is v3.3.2

Quality

chromeExtensionAsync has 0 bugs and 0 code smells.

Security

chromeExtensionAsync has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chromeExtensionAsync code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chromeExtensionAsync is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

chromeExtensionAsync releases are available to install and integrate.

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of chromeExtensionAsync

Get all kandi verified functions for this library.

chromeExtensionAsync Key Features

No Key Features are available at this moment for chromeExtensionAsync.

chromeExtensionAsync Examples and Code Snippets

No Code Snippets are available at this moment for chromeExtensionAsync.

Community Discussions

Trending Discussions on chromeExtensionAsync

How do I add a description to search on Bower.io?

QUESTION

How do I add a description to search on Bower.io?

Asked 2017-Apr-26 at 14:51

I have a component: chrome-extension-async published to both Bower and NPM.

When I search for it on bower.io it finds the package, but it doesn't find the description.

My bower.json has a description property.

libraries.io finds the component on both NPM and Bower, but the latter has no description (either from the json or the readme)

What am I doing wrong?

...

ANSWER

Answered 2017-Apr-26 at 14:25

Also by checking the code of libraries.io responsible for bower packages, it looks like everything is fine from this perspective. If you had changed your github repo name in the meantime though, that might very well be the issue.

My best bet would be a caching issue. If you had published it previously without description, libraries.io or bower.io might hold a cache of some fields like that, and I dunno really when it could be invalidated, you can also see you have 0 stars here which is not up-to-date.

I'm sure you already tried to bump the version, since as I can see from the bower.io api your did a last version on April 16. If you didn't thought, you might want to give it a try.

What I would advice you is to try changing your name to chrome-extension-async-tmp, and see if it gets picked up. If it does, that means it's something related to caching. In this case, you could (depending on your user-base) un-publish and republish the package, so the description gets picked up again.

After a simple clone and rename of your package, I published it on bower and 1 day later it was showing on the search results of both libraries.io and bower.io, with the correct descriptions. As you can see in their github.rake they are syncing repositories that have never been synced. Hopefully since #1080, they added a button to manually trigger a re-sync of a library if you are logged on the site (if no sync has occurred less than 24 hours ago). So I think that's what you're looking for.

Source https://stackoverflow.com/questions/43000658

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install chromeExtensionAsync

Or download chrome-extension-async.js file and include it directly:. TypeScript definitions for the altered API are in chrome-extension-async.d.ts. You must reference chrome-extension-async.js before your code attempts to use the features of this, as it needs to run across the Chrome API before you call it. <script async> is not currently supported, but you can use <script defer> so long as the scripts that use this are also defer and after it.
Note that you can use an ES5 build version of "Chrome Extension Async". Sometimes your application has a build process that requires you to use 3rd party libraries that published with ES5 code. For example, create-react-app will break the build and minification process if one of your dependencies is not published as standard ES5 code.

Support

This only 'promisifies' API functions that use callbacks and are not marked as deprecated. No backwards compatibility is attempted. Each API is added manually as JS can't spot deprecated or functions with no callbacks itself. Pull requests with additional API gratefully received.

Find more information at: