Reviewing next weekend. Thank you.

Hi @d4l3k

After reviewing the changes I've found the following issues:

• First of all, the file to edit is inside the src folder. When you launch the component's demo using npm start, it is copied with styles in the project's root. I have to document this.
• This change requires to use Browserify or another library to use require() in browser. I want to keep the component as standalone as possible.
• Finally, this change restores the full highlight.js download (more than 100kb). Recently I did a change to prevent this: Back to polymer element #14

I appreciate your contribution but I cannot approve it and merge for now. Maybe you can find another approach to make it work with Browserify that does not require to change the hightlight import inside code-sample.

Thank you.

You could provide two builds one with highlight.js compiled in and a second with highlight.js as the import. That way you'd be able to have both benefits with the same code base.

I believe most polymer3 apps use webpack anyways as that's the trend for JS frameworks. Not supporting the recommended way seems like the wrong approach.

Anyways, #17 makes this library a no-go for me so I switched to using the react highlight.js element and embedded it in my polymer3 app.

Ok, then I close the issue. I think that I can't do anything to fix the #17.
I'll investigate the two builds option.