open-text-editor-latest 1.0.3 → 1.0.6

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Danesh Naik
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/docs/PUBLISH.md

@@ -1,31 +1,31 @@
-# Publishing to npm
-
-Steps to publish a new version of `open-text-editor-latest`:
-
-1. Update `version` in `package.json` (follow semver).
-2. Commit your changes and push to your git repository.
-3. Ensure you are logged in to npm: `npm login`.
-4. Build the library (the `prepare` step is run automatically by `npm publish`, but you can run it manually to verify):
-
-```bash
-npm run build:lib
-```
-
-5. Publish to npm (public package):
-
-```bash
-npm publish --access public
-```
-
-Notes
-- The library build externalizes `react` and `react-dom`; they are declared as peer dependencies. Consumers must install React separately.
-- To test a local tarball before publishing, run:
-
-```bash
-npm pack
-# then install the produced tarball in another project (replace <version>):
-npm install ./open-text-editor-latest-<version>.tgz
-```
-
-- If you encounter npm tag/version errors (for example when attempting to publish a lower version than already published), either bump the package version in `package.json` or publish with an explicit tag: `npm publish --tag next --access public`.
-
+# Publishing to npm
+
+Steps to publish a new version of `open-text-editor-latest`:
+
+1. Update `version` in `package.json` (follow semver).
+2. Commit your changes and push to your git repository.
+3. Ensure you are logged in to npm: `npm login`.
+4. Build the library (the `prepare` step is run automatically by `npm publish`, but you can run it manually to verify):
+
+```bash
+npm run build:lib
+```
+
+5. Publish to npm (public package):
+
+```bash
+npm publish --access public
+```
+
+Notes
+- The library build externalizes `react` and `react-dom`; they are declared as peer dependencies. Consumers must install React separately.
+- To test a local tarball before publishing, run:
+
+```bash
+npm pack
+# then install the produced tarball in another project (replace <version>):
+npm install ./open-text-editor-latest-<version>.tgz
+```
+
+- If you encounter npm tag/version errors (for example when attempting to publish a lower version than already published), either bump the package version in `package.json` or publish with an explicit tag: `npm publish --tag next --access public`.
+

package/docs/USAGE.md

@@ -1,81 +1,81 @@
-Open Text Editor — Usage
-
-Install
-
-```bash
-npm install open-text-editor-latest
-```
-
-Basic usage
-
-```jsx
-import React, { useRef } from 'react'
-import OpenTextEditor from 'open-text-editor-latest'
-
-export default function App(){
-  const ref = useRef(null)
-
-  return (
-    <div style={{padding:20}}>
-      <OpenTextEditor
-        ref={ref}
-        initialValue={`<p>Hello</p>`}
-        onChange={(html) => console.log('changed', html)}
-      />
-    </div>
-  )
-}
-```
-
-Props
-- `initialValue` (string): optional initial HTML content
-- `onChange` (html: string) => void: optional change handler
-- `className` (string): optional additional class names applied to the editor container
-
-Peer dependencies
-
-This package expects React as a peer dependency (supported ranges: `^18 || ^19`). Install them if your project doesn't already include React:
-
-```bash
-npm install react@^18 react-dom@^18
-# or for React 19 consumers:
-npm install react@^19 react-dom@^19
-```
-
-Imperative API (via `ref`)
-
-When mounted with a `ref`, the editor exposes a small imperative API:
-
-- `focus()` — focus the editor
-- `getHtml()` — return current editor HTML
-- `setHtml(html)` — replace editor content
-- `insertHtml(html)` — insert HTML at the current selection
-- `execCommand(command, value)` — run low-level `document.execCommand`
-- `insertTable(rows, cols)` — insert a table programmatically
-- `tableAction(action)` — run table actions when a table cell is active
-
-Plugins
-
-Built-in plugin placeholders live in the source at `src/editor/plugins`. See [docs/editor/developer.md](editor/developer.md) for the plugin contract and examples.
-
-Building from source
-
-```bash
-git clone https://github.com/danu20002/open-text-editor.git
-cd open-text-editor
-npm install
-npm run build:lib
-```
-
-Local test
-
-```bash
-npm pack
-# install the generated tarball (replace <version> with the package version):
-npm install ./open-text-editor-latest-<version>.tgz
-```
-
-Publishing
-
-See [docs/PUBLISH.md](PUBLISH.md) for publish steps and notes about peer dependencies.
-
+Open Text Editor — Usage
+
+Install
+
+```bash
+npm install open-text-editor-latest
+```
+
+Basic usage
+
+```jsx
+import React, { useRef } from 'react'
+import OpenTextEditor from 'open-text-editor-latest'
+
+export default function App(){
+  const ref = useRef(null)
+
+  return (
+    <div style={{padding:20}}>
+      <OpenTextEditor
+        ref={ref}
+        initialValue={`<p>Hello</p>`}
+        onChange={(html) => console.log('changed', html)}
+      />
+    </div>
+  )
+}
+```
+
+Props
+- `initialValue` (string): optional initial HTML content
+- `onChange` (html: string) => void: optional change handler
+- `className` (string): optional additional class names applied to the editor container
+
+Peer dependencies
+
+This package expects React as a peer dependency (supported ranges: `^18 || ^19`). Install them if your project doesn't already include React:
+
+```bash
+npm install react@^18 react-dom@^18
+# or for React 19 consumers:
+npm install react@^19 react-dom@^19
+```
+
+Imperative API (via `ref`)
+
+When mounted with a `ref`, the editor exposes a small imperative API:
+
+- `focus()` — focus the editor
+- `getHtml()` — return current editor HTML
+- `setHtml(html)` — replace editor content
+- `insertHtml(html)` — insert HTML at the current selection
+- `execCommand(command, value)` — run low-level `document.execCommand`
+- `insertTable(rows, cols)` — insert a table programmatically
+- `tableAction(action)` — run table actions when a table cell is active
+
+Plugins
+
+Built-in plugin placeholders live in the source at `src/editor/plugins`. See [docs/editor/developer.md](editor/developer.md) for the plugin contract and examples.
+
+Building from source
+
+```bash
+git clone https://github.com/danu20002/open-text-editor.git
+cd open-text-editor
+npm install
+npm run build:lib
+```
+
+Local test
+
+```bash
+npm pack
+# install the generated tarball (replace <version> with the package version):
+npm install ./open-text-editor-latest-<version>.tgz
+```
+
+Publishing
+
+See [docs/PUBLISH.md](PUBLISH.md) for publish steps and notes about peer dependencies.
+

package/docs/editor/developer.md

@@ -1,37 +1,37 @@
-**Developer Guide — Plugins & Extensibility**
-
-This document explains the intended plugin contract and where built-in plugin placeholders live in the source tree.
-
-Plugin contract
-- A plugin should export a default function that accepts an `editorApi` object and returns an object with:
-  - `name` — plugin id string
-  - `install()` — called when the plugin is enabled; register commands, toolbar buttons, or event listeners here
-
-Example plugin skeleton
-```js
-export default function myPlugin(editorApi) {
-  return {
-    name: 'my-plugin',
-    install() {
-      // Example: add a simple command that inserts a timestamp
-      const insertTimestamp = () => editorApi.insertHtml(`<time>${new Date().toISOString()}</time>`)
-      // Optionally expose commands or UI wiring via editorApi
-      editorApi.registerCommand && editorApi.registerCommand('insert-timestamp', insertTimestamp)
-    }
-  }
-}
-```
-
-Built-in plugins
-- Built-in plugin placeholders are in the source at `src/editor/plugins/` (part of this repo). Consumers installing the package get the compiled library; to inspect or extend built-ins, open the repository and edit or copy the plugin files from that folder.
-
-Registering plugins (current status)
-- This release provides plugin scaffolding in source. Runtime plugin registration APIs (for consumer-supplied plugins) are planned; for now you can compose plugins in your app by importing their code or by modifying the source plugin folder when building from source.
-
-Best practices
-- Keep plugins small and focused.
-- Prefer declarative UI for toolbar buttons (icon, tooltip, command).
-- Clean up event listeners and DOM mutations during uninstall.
-
-If you want, I can implement a runtime `editorApi.registerPlugin()` and `editorApi.addToolbarButton()` API in `src/editor/OpentextEditor.jsx` so consumers can register plugins dynamically. Say the word and I will wire it up and add examples.
-
+**Developer Guide — Plugins & Extensibility**
+
+This document explains the intended plugin contract and where built-in plugin placeholders live in the source tree.
+
+Plugin contract
+- A plugin should export a default function that accepts an `editorApi` object and returns an object with:
+  - `name` — plugin id string
+  - `install()` — called when the plugin is enabled; register commands, toolbar buttons, or event listeners here
+
+Example plugin skeleton
+```js
+export default function myPlugin(editorApi) {
+  return {
+    name: 'my-plugin',
+    install() {
+      // Example: add a simple command that inserts a timestamp
+      const insertTimestamp = () => editorApi.insertHtml(`<time>${new Date().toISOString()}</time>`)
+      // Optionally expose commands or UI wiring via editorApi
+      editorApi.registerCommand && editorApi.registerCommand('insert-timestamp', insertTimestamp)
+    }
+  }
+}
+```
+
+Built-in plugins
+- Built-in plugin placeholders are in the source at `src/editor/plugins/` (part of this repo). Consumers installing the package get the compiled library; to inspect or extend built-ins, open the repository and edit or copy the plugin files from that folder.
+
+Registering plugins (current status)
+- This release provides plugin scaffolding in source. Runtime plugin registration APIs (for consumer-supplied plugins) are planned; for now you can compose plugins in your app by importing their code or by modifying the source plugin folder when building from source.
+
+Best practices
+- Keep plugins small and focused.
+- Prefer declarative UI for toolbar buttons (icon, tooltip, command).
+- Clean up event listeners and DOM mutations during uninstall.
+
+If you want, I can implement a runtime `editorApi.registerPlugin()` and `editorApi.addToolbarButton()` API in `src/editor/OpentextEditor.jsx` so consumers can register plugins dynamically. Say the word and I will wire it up and add examples.
+

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "open-text-editor-latest",
   "private": false,
-  "version": "1.0.3",
+  "version": "1.0.6",
   "type": "module",
   "description": "A lightweight, pluggable React contentEditable rich text editor",
   "scripts": {
@@ -34,7 +34,7 @@
     "vite": "^7.2.4"
   },
   "main": "dist/index.cjs.js",
-  "module": "dist/index.es.js",
+  "module": "dist/index.esm.js",
   "files": [
     "dist/",
     "src/editor/",
@@ -64,7 +64,7 @@
   },
   "exports": {
     ".": {
-      "import": "./dist/index.es.js",
+      "import": "./dist/index.esm.js",
       "require": "./dist/index.cjs.js"
     }
   }