1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-24 10:27:10 +02:00
joplin/packages/renderer
2021-12-27 18:00:01 +01:00
..
assets All: Update Mermaid: 8.12.1 -> 8.13.5 (#5831) 2021-12-13 10:35:21 +00:00
lib
MdToHtml Security: Ensure Markdown links that contain single quotes are correctly escaped 2021-11-08 15:39:45 +00:00
tests
Tools
vendor
.gitignore
assetsToHeaders.js
defaultNoteStyle.js
headerAnchor.ts Server: Added Help page for Joplin Cloud 2021-08-31 13:46:46 +01:00
HtmlToHtml.ts Server: Fixed publishing of notes with HTML markup type 2021-08-12 17:23:49 +01:00
htmlUtils.ts Desktop, Mobile: Fixes #5687: Fixed issue with parts of HTML notes not being displayed in some cases 2021-11-09 18:33:28 +00:00
index.ts Server: Added Help page for Joplin Cloud 2021-08-31 13:46:46 +01:00
InMemoryCache.ts
jest.config.js
MarkupToHtml.ts Desktop: Allow setting a max width for the editor content 2021-08-14 12:19:53 +01:00
MdToHtml.ts Tools: Use Yarn 3 to manage monorepo (#5833) 2021-12-20 15:08:43 +00:00
noteStyle.ts Desktop: Resolves #5740: Make code blocks horizontally scrollable on note viewer 2021-11-17 19:46:00 +00:00
package.json Setup new release 2.7 2021-12-27 17:56:59 +01:00
pathUtils.ts
publish.sh Tools: Switched to npm version patch since it is not available in yarn 2021-12-27 18:00:01 +01:00
README.md
stringUtils.js
tsconfig.json
urlUtils.js
utils.ts

Joplin Renderer

This is the renderer used by Joplin to render notes in Markdown or HTML format.

Installation

npm i -s joplin-renderer

Certain plugins require additional assets like CSS, fonts, etc. These assets are in the /assets directory and should be copied to wherever the application can find them at runtime.

Usage

const { MarkupToHtml } = require('joplin-renderer');

const options = {};

// The notes are rendered using the provided theme. The supported theme properties are in `defaultNoteStyle.js`
// and this is what is used if no theme is provided. A `theme` object can be provided to override default theme
// properties.
const theme = {};

const markdown = "Testing `MarkupToHtml` renderer";

const markupToHtml = new MarkupToHtml(options);
const result = await markupToHtml.render(MarkupToHtml.MARKUP_LANGUAGE_MARKDOWN, markdown, theme, options);

console.info('HTML:', result.html);
console.info('Plugin assets:', result.pluginAssets);

When calling render(), an object with the following properties is returned:

  • html: The rendered HTML code
  • pluginAssets: The assets required by the plugins

The assets need to be loaded by the calling application. For example this is how they are loaded in the Joplin desktop application:

function loadPluginAssets(assets) {
	for (let i = 0; i < assets.length; i++) {
		const asset = assets[i];

		if (asset.mime === 'text/css') {
			const link = document.createElement('link');
			link.rel = 'stylesheet';
			link.href = 'pluginAssets/' + asset.name;
			document.getElementById('joplin-container-styleContainer').appendChild(link);
		}
	}
}

Development

Updating a markdown-it plugin

Whenever updating a Markdown-it plugin, such as Katex or Mermaid, make sure to run npm run buildAssets, which will compile the CSS and JS for use in the Joplin applications.

Adding asset files

A plugin (or rule) can have any number of assets, such as CSS or font files, associated with it. To add an asset to a plugin, follow these steps:

  • Add the file under /assets/PLUGIN_NAME/your-asset-file.css
  • Register this file within the plugin using context.pluginAssets[PLUGIN_NAME] = [{ name: 'your-asset-file.css' }]

See katex.js for an example of how this is done.

Adding inline CSS

A plugin can ask for some CSS to be included inline in the rendered HTML. This is convenient as it means no extra file needs to be packaged. Use this syntax to do this:

context.pluginAssets[PLUGIN_NAME] = [
	{
		inline: true,
		text: ".my-css { background-color: 'green' }",
		mime: 'text/css',
	},
];