This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 227620 - ServerSide Javascript Support
Summary: ServerSide Javascript Support
Status: NEW
Alias: None
Product: javascript
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal with 3 votes (vote)
Assignee: Petr Pisl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-18 13:11 UTC by tdev
Modified: 2014-10-06 13:06 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tdev 2013-03-18 13:11:28 UTC
Product Version = NetBeans IDE 7.3 (Build 201302132200)

Allow in HTML Project  a WebPage  like in PHP Project
(Or allow in PHP Project Properties  JavaScriptFiles like in HTML Project properties)

A WebPage or better Template should support different syntax e.g  <%,  {{ or whatever  
Actual a PHP web page needs <?php  to get code completion

In summary provide a new project type that is more sophisticated for serverside Javascript 
development, testing, debugging, building etc,  e.g for nodejs, ...
Comment 1 Philzen 2014-05-06 03:05:45 UTC
There is http://plugins.netbeans.org/plugin/36653/nodejs which does provide a separate project type, completely based around the package.json file.

Unfortunately on my install (NB 8.0 Build 201403101706) the editor won't activate full ecmascript support (i.e. code-completion "No suggestions") with that - otherwise it's neat imho, i use it to generate and manage anything that doesn't require a full HTML5 project type, but a package.json and git integration.

So, summarizing the top-requirements:
- a project type with basic package management capabilities like the one the plugin provides (perhaps integrate the plugin into netbeans)
- full ecmascript 5+ support enabled as a priority
- include library stubs with js doc for core nodejs features (require, fs, ...)
- other html5 / css per features per ondemand activation (if feasible deactivate by default)
- basic debugging / tracing features

Excluding the last requirement this sounds like the pieces of the puzzle are already there to be put together by someone who knows (or can advice) how.