[wp-trac] [WordPress Trac] #29546: grunt uglify for plugins and plugin developers

[WordPress Trac]

#29546: grunt uglify for plugins and plugin developers
------------------------------+--------------------
 Reporter:  MattyRob          |       Owner:
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  4.1
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  trivial           |  Resolution:
 Keywords:  has-patch         |     Focuses:
------------------------------+--------------------

Comment (by netweb):

 I knew I forgot to follow up something somewhere...

 As I stated in #28464 :
 > 1) This task will only run JSHint on plugins being developed in `\src
 \wp-content\plugins`
 > * If a plugin developer needs, and I believe that they should, they
 should be running WordPress trunk from `/build` via the `develop.svn` repo
 or they should use `core.svn` to develop their plugin.
 >
 > * Developing plugins by loading WordPress via `\src\wp-content\plugins`
 of the `develop.svn` repo excludes RTL CSS or admin themes CSS (Midnight,
 Ocean etc) and I think we should be encouraging plugin authors to test
 their plugins for compatibility with these core features.
 I should have included in that original statement that minified CSS and
 JavaScript files also do not exist (bar a handful of exceptions) in the
 `/src` folder of the `develop.` repo.

 I am all for making available and utilising Core's Grunt tools to help
 plugin and theme authors, just at this stage adding what is outlined in
 this ticket in my opinion is clunky at best. Testing any theme or plugin
 in the `/src` folder without Core's minified CSS/JS is not testing we
 should be encouraging as utilising the `SCRIPT_DEBUG` constant in this use
 case with Uglify would not result in accurate nor reliable testing.

 At this stage I still stand by that we should not be encouraging
 plugin/theme authors to develop their plugin/theme in the `/src` folder of
 the `develop.` repo whilst there are parts of WordPress Core that are non-
 existent in this folder.

 I'd love to have workable solution that would allow this to be the case,
 where the developer develops in the `/src` folder and WordPress Core's
 Grunt tools can perform at least everything that the current Core tools
 can and copy/build everything into the `/build` folder where the developer
 has their WordPress install configured to run via the '/build` folder.

 Plugin and theme authors should be using either `core.` SVN/Git repo or
 use a custom `wp-content` folder alongside the `/build` folder of the
 `develop.` SVN/Git repo.

--
Ticket URL: <https://core.trac.wordpress.org/ticket/29546#comment:12>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform