UNPKG

@merkur/plugin-http-client

Version:

Merkur event emitter plugin.

15 lines (9 loc) 1.43 kB
# Merkur - plugin-http-client [![Build Status](https://github.com/mjancarik/merkur/workflows/CI/badge.svg)](https://travis-ci.com/mjancarik/merkur) [![NPM package version](https://img.shields.io/npm/v/@merkur/plugin-http-client/latest.svg)](https://www.npmjs.com/package/@merkur/plugin-http-client) ![npm bundle size (scoped version)](https://img.shields.io/bundlephobia/minzip/@merkur/plugin-http-client/latest) [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier) The HTTP client plugin adds http property to your widget with a request method. Under the hood this plugin uses native browser fetch API and for server-side the node-fetch polyfill. **[Documentation for @merkur/plugin-http-client](https://merkur.js.org/docs/http-client-plugin).** ## About Merkur The [Merkur](https://merkur.js.org/) is tiny extensible javascript library for front-end microservices. It allows by default server side rendering for loading performance boost. You can connect it with other frameworks or languages because merkur defines easy API. You can use one of four predefined template's library [Preact](https://preactjs.com/), [µhtml](https://github.com/WebReflection/uhtml#readme), [Svelte](https://svelte.dev/) and [vanilla](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals) but you can easily extend for others.