remove main field from package.json

[huozhi]

• prism-themes is a pure css package, doesn't have to contain a main field
• there's issue when prism-themes as dependency. like bundler might traverse dependency and pre-bundle/pre-compile it.

e.g. browserless is depending on prism-themes. when I use pkg to bundle a script using browserless. prism-themes is failed to be bundled

[RunDevelopment]

I can see that main: README.md doesn't make much sense but will removing the main field help? From my understanding, a missing main field is roughly equivalent to main: index.js.

[huozhi]

@RunDevelopment I'm not sure how bundler handle package with any entry. If it's required to have one, do you feel it's proper to change the main entry to a empty one, like fbjs/index.js ?

// index.js
throw new Error('This package should not be required without a full path.');

[RunDevelopment]

Hmmm, I don't really like having a useless JS file just work around this.

Question: Have you checked that removing the main field actually fixes your problem? If it works with the bundler you use, it'll probably also work with others.

[huozhi]

yeah I've tested locally with removing main field from package.json in node_modules, problem solved. I'd expect regular css imports with absolute path won't cause this issue.

[RunDevelopment]

If it works for you, it'll probably also work for others. Right now, it just can't work, so let's merge this.

[huozhi]

Thank you @RunDevelopment