Mohammad Asif cf937194cb Removed un-waned things 1. 5 months ago
..
CHANGELOG.md cf937194cb Removed un-waned things 1. 5 months ago
LICENSE cf937194cb Removed un-waned things 1. 5 months ago
README.md cf937194cb Removed un-waned things 1. 5 months ago
browser.d.ts cf937194cb Removed un-waned things 1. 5 months ago
browser.js cf937194cb Removed un-waned things 1. 5 months ago
node.d.ts cf937194cb Removed un-waned things 1. 5 months ago
node.js cf937194cb Removed un-waned things 1. 5 months ago
package.json cf937194cb Removed un-waned things 1. 5 months ago

README.md

@sanity/eventsource

npm stat npm version gzip size size

Meta-package to make browsers and Node use different EventSource polyfills

npm install @sanity/eventsource

Usage

import polyfilledEventSource from '@sanity/eventsource'

The polyfill adds support for auth headers, which isn't part of the EventSource spec.

In NodeJS environments it's the implementation from eventsource package. While browsers use event-source-polyfill.

Forcing a specific implementation

To get the browser implementation, no matter how your bundler or runtime understands package.json exports, you can use the following:

import polyfilledEventSource from '@sanity/eventsource/browser'

To force the Node implementation, use the following:

import polyfilledEventSource from '@sanity/eventsource/node'

Release new version

Run "CI & Release" workflow. Make sure to select the main branch and check "Release new version".

Semantic release will only release on configured branches, so it is safe to run release on any branch.

License

MIT © Sanity.io