Wild Web Developer: HTML, CSS, JavaScript, TypeScript, Node.js, Angular, JSON, YAML (+Kubernetes), XML
Details Group Tabs
Saturday, September 19, 2020 - 23:14
Reviews Sign in to post reviews
Breaking up as it runs slow with a beefed up DEV PC.
Submitted by Jo Ruiz on Tue, 2020-09-01 11:29
An instance of Eclipse running these plugins runs 4 to 6 instances of Node.js Server, which inturn takes up a ton of CPU resources. When an edit is made to a ts or html file the CPU usage spikes.
Bloating everything together seems to be over kill, as this also slows the development environment so much that I just don't want to use this product anymore and would rather just use an Outdated or none at all.
Re: Breaking up as it runs slow with a beefed up DEV PC.
Submitted by Mickael Istria on Fri, 2020-09-04 09:42
Please report issues to https://github.com/eclipse/wildwebdeveloper/issues
Can you consider breaking up
Submitted by Alex Aiezza on Mon, 2020-07-27 15:31
Can you consider breaking up the pieces of this plugin?
I only want a Typescript editor in Eclipse. SO much of this plugin I do not want in my installation.
I should be able to pick and choose from the marketplace installation window what actually gets installed.
Re: Can you consider breaking up
Submitted by Gautier De SAINT MARTIN LACAZE on Tue, 2020-07-28 18:38
Hello,
Thanks for sharing your concern about WWD. Can you create an issue here https://github.com/eclipse/wildwebdeveloper/issues to continue the discussion?
Thanks.
Problems/bugs in Windows 10 (64bit) + Eclipse 2019-09 R (4.13.0)
Submitted by John C on Tue, 2019-12-10 06:36
I have been using the Angular Eclipse (by Angelo ZERR) plugin for a couple of years, but decided to give the Wild Web Developer plugin a try today, although with limited success.
The first hurdle was a dialog (actually dozens of them, which appear repeatedly after any mouse movement over a source file) saying "Node.js version could not be determined. Please make sure a supported version of node.js is installed, editors may be missing key features otherwise. Supported major versions are: 8, 9, 10, 11, 12, 13".
I have version 10.17.0 installed in "C:\Program Files\nodejs", but WWD does not appear to be able to detect it correctly. After searching extensively for this error message (again, mostly unsuccessfully), I eventually landed on the Github page for the source file involved in the node version check (github.com/jabby/wildwebdeveloper/commit/20149e1a6913f309d47de25b8c5174375553d0a9#diff-bc8d0fb247d15f842c56c8acda87abad).
The code shows that the builtin "where" command is used to locate the path to the node executable (in my case C:\Program Files\nodejs\node.exe). The returned path is then executed with the "-v" option to obtain the version of Node. However I suspect that the command is not being correctly executed (due to the space in the path?) because the code is unable to determine the version of Node, even though the executable exists.
I then realised that the path could be forced by adding "-Dorg.eclipse.wildwebdeveloper.nodeJSLocation=C:\Program Files\nodejs\node.exe" to the eclipse.ini file. This did indeed allow me to open Eclipse without being bombarded with dialog messages (note to devs, I think a single error message, or at most one error per filetype, and per session should be sufficient, and not a dozen (or more) every time the mouse moves a pixel over a source file!)
Although setting the path directly in the ini file solves the immediate problem, if Eclipse is restarted (File -> Restart) the ini file is not read and the global property is no longer set - resulting in the reappearance of the dozens of popup error messages.
But perhaps that's a problem that should be reported to the Eclipse team.
After finally getting the plugin installed and reopening my TS and HTML files with the Generic Text Editor, I was immediately presented with a bunch of red error markers. Some of the (Angular) errors are useful (unused imports etc.) but some, for example "let- is only supported in ng-template elements" and "Component '...' is not included in a module and will not be available inside a template..." are irritating, to say the least, because they appear to refer to restrictions implemented in later versions of Angular than the one I am using (2.0), and there does not appear to be any way to disable or configure them.
And finally, the plugin org.eclipse.lsp4e (installed with WWD) appears to have some issues, given the number of problems that are being logged in the Error log pane. For example:
and
and finally
In summary, as much as I would like to use this new and improved (?!) plugin, it doesn't yet appear to be ready for general use (or maybe I'm just unlucky?!). So I guess I'll be going back to the original Angular Eclipse plugin - it's not perfect, but is at least more stable than the current version of WWD.
Please use https://github.com
Submitted by Mickael Istria on Wed, 2019-12-18 09:18
Please use https://github.com/eclipse/wildwebdeveloper/issues to report bugs or ask for support.
first installation and using
Submitted by Ivan Semikin on Wed, 2019-07-03 07:20
I have "Eclipse Wild Web Developer" pugun installed, There is still no editiing tip in .js files.
I used these instructions on github:
Install into Eclipse IDE (pick one way or another):
With Eclipse Marketplace Client and https://marketplace.eclipse.org/content/wild-web-developer-web-developme..., choose one of:
Help > Eclipse Marketplace, search Wild Web Developer then click Install or
drag into Eclipse IDE, or
With Help > Install New Software... with p2 repo http://download.eclipse.org/wildwebdeveloper/snapshots
Re: first installation and using
Submitted by Mickael Istria on Tue, 2019-08-13 02:53
Please report issue or ask for support by using GitHub issues.
JSON Formatting doesn't work
Submitted by Igor Khlaponin on Tue, 2019-04-09 03:19
This plugin is pretty cool. But the major issue, as for me, is JSON formatting. I cannot format JSON neither through Ctrl+Shift+F nor through RMB->Format (this menu item even inactive). On the other hand, code completion works as expected.
OS: Centos 7, Java 8, Eclipse 2018-12
P.S. Kubernetes schema support is awesome!
Re: JSON Formatting doesn't work
Submitted by Mickael Istria on Tue, 2019-04-09 09:03
Thanks, can you please report this issue to https://github.com/eclipse/wildwebdeveloper/issues and we'll investigate it, and hopefully ship it soon ;)
Re: Re: JSON Formatting doesn't work
Submitted by Igor Khlaponin on Wed, 2019-04-10 14:55
Done. Eclipse marketplace doesn't allow external links, so I sent it you in Twitter