prettier dependency? about chrome-extension-tools HOT 5 CLOSED

Oh btw, the way I fixed my problem:

1. change rollup-plugin-chrome-extension/package.json > to read "prettier": "^2.3.2", (latest stable)
2. npm i prettier at project level.
3. del package-lock.json
4. npm i at project level.

I didn't have prettier installed at proj level before, and that alone may have fixed it.

from chrome-extension-tools.

@ogrotten Weird. I've had that same problem, so I'm glad that you found a solution! Svelte is great for Chrome Extensions, isn't it?

I'll see if we can remove prettier. Thanks for isolating the problem.

from chrome-extension-tools.

The way I removed it isn't a fix. It results in the compiler complaining about "prettier is missing". I just did that to see if that instance of prettier was at the core of my problem, and it was.

Other than that, I dug around. . . there's only 1 real reference to it, and it appears to be rewriting the derived html output to be prettied for source. I tried to modify it, but I don't know all the ins n outs.

I don't think prettier is necessary tho... all modern browsers (even safari) will reformat and Pretty Print even the jankiest html source in their inspector.

And yeah . . . I'm liking svelte + extensions!

from chrome-extension-tools.

You're right tho, we didn't need it!

I was able to remove it, and prettier is only a dev dependency in the latest beta release.

I'm in the middle of adding MV3 support, but all the MV2 tests are passing, so it should work just fine.

from chrome-extension-tools.

Badass! Glad to have helped!

from chrome-extension-tools.