https://github.com/bahrus/k-fetch
k-fetch is a small, bare-bones simple fetch web component.
https://github.com/bahrus/k-fetch
custom-element custom-elements custom-elements-v1 web-component web-components
Last synced: 4 months ago
JSON representation
k-fetch is a small, bare-bones simple fetch web component.
- Host: GitHub
- URL: https://github.com/bahrus/k-fetch
- Owner: bahrus
- License: mit
- Created: 2020-12-11T20:53:00.000Z (over 4 years ago)
- Default Branch: baseline
- Last Pushed: 2024-03-09T12:08:51.000Z (over 1 year ago)
- Last Synced: 2025-02-01T01:34:21.568Z (4 months ago)
- Topics: custom-element, custom-elements, custom-elements-v1, web-component, web-components
- Language: TypeScript
- Homepage: https://jsfiddle.net/bahrus/ma0vtbnx/2/
- Size: 322 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# k-fetch
[](http://badge.fury.io/js/k-fetch)
[](https://bundlephobia.com/result?p=k-fetch)
## [Demo](https://jsfiddle.net/bahrus/ma0vtbnx/1/)
k-fetch is a small, bare-bones simple fetch web component. For more features (but larger footprint), see [xtal-fetch](https://www.npmjs.com/package/xtal-fetch). k-fetch provides no support for rendering while streaming. For such support, see alternatives, such as [be-written](https://github.com/bahrus/be-written).
k-fetch can act as a base web component for "web components as a service". [be-kvetching](https://github.com/bahrus/be-kvetching) and [be-fetching](https://github.com/bahrus/be-fetching) [TODO] actually do just that - they can dynamically create such a web component on the fly, declaratively, that extends this base class.
Markup:
```html
```
For this very specific example shown above, due to restrictions of the cors-anywhere utility the link above uses, you will first need to go to https://cors-anywhere.herokuapp.com/corsdemo to unlock the service for a limited amount of time.
Required attributes are href and at least one of these attributes: onerror, oninput, onload, onchange. The reason for insisting on at least one of these on* attributes is this: Since these attributes can't pass through any decent sanitizer that prevents xss attacks, the presence of one or more of them indicates that the web site trusts the content from which the data is being retrieved.
When the fetch is complete, event "load" is fired, which can allow for manipulation of the data. The (modified) data is then stored in the "value" field of the k-fetch (or subclassed) instance. Also, event "change" is fired.
If as=html, the response is inserted into the innerHTML of the k-fetch element, unless attribute shadow is present, in which case it will first create a shadowRoot, then insert the innerHTML.
k-fetch has no support for "href" or "as" properties, only attributes.
k-fetch caches get's based on the localName of the custom element as the base key of the cache.
## Sending data to a target:
```html
...
```
k-fetch will set aria-busy to true while fetch is in progress, and also set aria-live=polite if no aria-live value is found.
## Viewing Demos Locally
Any web server that can serve static files will do, but...
1. Install git.
2. Fork/clone this repo.
3. Install node.js.
4. Open command window to folder where you cloned this repo.
5. > npm install
6. > npm run serve
7. Open http://localhost:3030/demo/ in a modern browser.
## Using from ESM Module:
```JavaScript
import 'k-fetch/k-fetch.js';
```
## Using from CDN:
```html
import 'https://esm.run/k-fetch';
```