Polymer & Web Components
JetBrainsJetBrains · v—
Adds support for building encapsulated, reusable web components via the Polymer library.
Rating distribution
Reviews 8
Well, the support is already pretty good, but there are some features missing and so there are always some weak errors when you don't suppress the `JSUnresolvedGlobalSymbols` and `JSUnresolvedVariable`. So my question is, is there maybe an open source version of this plugin, that maybe I can support your work on this plugin?
There seem to still be problems with CPU consumption. While working with the plugin enabled, IDEA suddenly (after some minutes of working) takes 100% CPU (JVisualVM says, it's some scheduled Jobs). When I disable the plugin in such a situation, the CPU consumption instantly drops to ~0.
I can never get this plugin to quite work out as well as it should, and i definitely get problems with CPU issues on a MBP. Any way you can open this up to the public to allow for some of us who desperately need this fixed, to fix it for ya?
worst extension
This plugin seems like another attempt by JetBrains to check a box for marketing reasons without actually supporting a platform well. This plugin is severely lacking in it's understanding of Polymer Web Components (like LitElement). Even the most basic aspects like the css tag and customeElement decorator are not yet fully working. TL;DR If you write Polymer code move over to VSCode for now.
Latest versions cannot be installed with WebStorm 2018.x. WS 2018.1.x has an older version of this plugin. WS 2018.2 finds in the repo only the version 182.2371.6. The last one is 183.3283.3 which I tried to install from disk but it says it's "incompatible with this installation". Polymer is going down but Web Components are on the rise so the need for such a plugin is increasing... Thanks...
Oh, I activated 182.2371.6 and it's broken: now it won't recognize basic objects such as window, document, and other defined objects in the script. Deactivated instantly :(
Despite the recent updates, this plugin doesn't recognize webcomponents I think it happens since custom elements specification reached *v1*