Add standalone build

[cfraz89]

The standalone build allows the plugin to be used in the browser, prettier/standalone. Allows for features such as in-browser formatting and codemods.

Have added an exports field to package.json to ensure the correct standalone/node/esm/cjs version of the package is used based on environment.

I've also changed the 'svelte' exclude to 'svelte/compiler' in the standalone rollup configs, as the compiler was getting bundled in and I have the feeling it isnt intended to be. If this is the case, you may want to adjust the standard rollup config too.

[dummdidumm]

Thanks! Could you tell me how to test this out locally?

[cfraz89]

Thanks! Could you tell me how to test this out locally?

Try putting together a svelte page like this:

<script>
import * as sveltePlugin from 'prettier-plugin-svelte';
import prettier from 'prettier/esm/standalone';
import babelParser from 'prettier/esm/parser-babel';
import cssParser from 'prettier/esm/parser-postcss';

const formatted = prettier.format('<script>const thisIsCode = 1;</script><style></style><div>Svelte source code here</div>', {
		parser: 'svelte',
		plugins: [sveltePlugin, babelParser, cssParser]
	});
</script>

<div>{formatted}</div>

I havent used that exact code myself, so there may be a small issue in there somewhere.

If you're using it in sveltekit, you'll need a svelte.config.js kit.vite section like

	kit: {
	       ...,
		vite: {
			optimizeDeps: {
				exclude: ['prettier-plugin-svelte', 'prettier']
			},
			ssr: {
				noExternal: ['prettier']
			}
		}
	}

Let me know if you have any troubles and I can put up a demo page.

[dummdidumm]

Sorry for the long delay. I left some comments, let me know what you think.

[dummdidumm]

Instead of adding a dependency on buffer, could we instead do something like

// base64-string.ts
export const stringToBase64 = (str: string) => typeof btoa !== 'undefined' ? bota : Buffer.from(str).toString('base64');
export const base64ToString = (str: string) => typeof atob !== 'undefined' ? bota : Buffer.from(str, 'base64').toString();

and use that file in the appropriate places?

[curran]

Agree that the buffer dependency feels sketchy.

[dummdidumm]

I don't see this file generated anywhere according to the rollup configs. Oversight?

[dummdidumm]

To save some bytes when publishing: Could we only publish the plugin map, not the standalone map?

[dummdidumm]

For even more compatibility, add standalone.js to the top level browser field?

[curran]

See also #417