https://github.com/nextjournal/prosemirror-gapcursor-bug
Using the codemirror example from ProseMirror’s website to debug a potential gap cursor regression
https://github.com/nextjournal/prosemirror-gapcursor-bug
Last synced: 11 months ago
JSON representation
Using the codemirror example from ProseMirror’s website to debug a potential gap cursor regression
- Host: GitHub
- URL: https://github.com/nextjournal/prosemirror-gapcursor-bug
- Owner: nextjournal
- License: mit
- Created: 2019-11-06T11:46:47.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2022-03-25T18:01:52.000Z (almost 4 years ago)
- Last Synced: 2025-02-16T15:06:22.001Z (11 months ago)
- Language: JavaScript
- Size: 1.16 MB
- Stars: 1
- Watchers: 5
- Forks: 0
- Open Issues: 5
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Prosemirror.net
These are the sources for http://prosemirror.net
This currently contains a [front-page](http://prosemirror.net), the
[examples](http://prosemirror.net/examples/) (including server-side code to
support the
[collaborative demo](http://prosemirror.net/example/collab/)), the
[guide](http://prosemirror.net/docs/guide/), and the scripts to build
the [reference docs](http://prosemirror.net/docs/ref/).
## Installation
Install [Node.js](http://nodejs.org).
Install the module's dependencies:
```bash
npm install
```
Build the documentation and all the demos' JavaScript source
```bash
make
```
That will populate the `public/` directory with an instance of the
website. You could point a webserver at it to try it out.
To work on the demos, or to experiment with the collaborative demo, it
is a good idea to use the dev server:
```
npm run devserver -- --port 8888
```
That will get you a server at [localhost:8888](http://localhost:8888/)
that serves the files in `public/`, along with the collaborative
editing backend, and updates the demo pages to use
[moduleserve](https://github.com/marijnh/moduleserve) so that you can
run the demos directly from the source files, rather than using the
bundled code. You can now edit them and see the changes with a single
refresh. (Though the server-side collaborative code still needs a
server refresh to update.)
Note that this is not secure (it provides filesystem access of HTTP)
and not fast (the browser will fetch each module individually), and
should only be used for development, on your local machine, bound to
`localhost`.