Closed rhystmills closed 5 months ago
I was having trouble running this locally - some obscure bug was causing all text nodes in our Composer editor to show as the string 'undefined', I've now released a more simpler fix to get the build running: https://github.com/guardian/prosemirror-noting/pull/55
What does this change?
This PR moves the build process from Rollup to Vite, removes many now-unused dependencies, and bumps the version of many remaining dependencies.
Running
yarn build
was failing for me - possible due to some clashes in dependency changes since the last release (four years ago). I had a go at bumping various packages but kept encountering errors related to either rollup or eslint. With so many linked dependencies, it was difficult to isolate which one was at the route of the problem.I've decided instead to remove rollup completely, and replace with Vite. Vite is used more widely in Content Production, especially in related packages like https://github.com/guardian/prosemirror-typerighter and https://github.com/guardian/prosemirror-editor
eslint
has been modernised, using the new config format, replacing.eslintrc.json
.How to test
yarn
thenyarn build
locally in this project. Does it build?noting.js
andnoting.css
in the top leveldist
folder.You could also try publishing locally with
yarn yalc
and then use it in flexible-content (viayalc add @guardian/prosemirror-noting
in the composer directory).