Mark Silverwood

Thank you for your feature request for Lightweight Charts. In order to keep the library lightweight and maintain a narrow focus, we strive to include only strictly required features in...

Most of those search results are `plugin-lwc` or `lwc-*-plugin` which aren't an exact match for the prefix of `lwc-plugin-*`. Checking the keyword on NPM, shows only lightweight chart plugins (they...

Thank you for your feature request for Lightweight Charts. In order to keep the library lightweight and maintain a narrow focus, we strive to include only strictly required features in...

We recently introduced the ability to write plugins for Lightweight Charts, allowing users like you to extend the functionality of the library without adding it to the core. These plugins...

This issue has been resolved with the [`v4.0.0`](https://github.com/tradingview/lightweight-charts/releases/tag/v4.0.0) release.

Thank you for your feature PR for Lightweight Charts. In order to keep the library lightweight and maintain a narrow focus, we strive to include only strictly required features in...

### FYI: Results of running [`publint`](https://publint.dev). ```bash npm run prepare-release npx publint ``` #### Master ``` lightweight-charts lint results: Suggestions: 1. pkg.module is used to output ESM, but pkg.exports is...

@Nipheris I've added back `index.cjs`. It's specified as the `main` key on the package.json as a fallback for older versions of node, and under the `"require"` sections of `"exports"`. This...

- Added `cjs` builds (thanks @Nipheris), and added a standalone esm version. The standalone esm version would allows users to use the import syntax directly in the browser without a...

> > Older versions of node and bundlers will use this as the fallback while the newer versions will use the values defined in the exports field. > > Tbh...