[
https://issues.apache.org/jira/browse/NETBEANS-2145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16773045#comment-16773045
]
Iván Barták edited comment on NETBEANS-2145 at 2/20/19 2:07 PM:
----------------------------------------------------------------
The specific problem for Sass is the fallowing:
Till now the official one was ruby-sass. And it needs cache files or no-cache
option. In order not to clutter the project folder, the --cache-location
parameter is hard coded.
But now the dart-sass version is the official one. And it throws {{Could not
find an option named "cache-location"}}. error.
*So anybody uses old ruby version needs the parameter, but other builds throws
error because of it.*
To tackle issues like this for example Jetbrains has configurable parameter
string for all console calls like this:
{{--no-cache $FileNameWithoutExtension$.css:$FileNameWithoutExtension$.css.map}}
In this scenerio the user can decide weather use cache-location, no-cache or
just remove both for the new official version. Even could use {{--output-style
compressed}} to get compressed css for production instantly.
This applies to all of the console tools, in most cases would be nice to be
able configure those, but sometimes its inevitable.
was (Author: montaire):
The specific problem for Sass is the fallowing:
Till now the official one was ruby-sass. And it needs cache files or no-cache
option. In order not to clutter the project folder, the --cache-location
parameter is hard coded.
But now the dart-sass version is the official one. And it throws {{Could not
find an option named "cache-location"}}. error.
*So anybody uses old ruby version needs the parameter, but other builds throws
error because of it.*
To tackle issues like this for example Jetbrains has configurable parameter
string for all console calls like this:
{{--no-cache}}{{
$FileNameWithoutExtension$.css:$FileNameWithoutExtension$.css.map}}
In this scenerio the user can decide weather use cache-location, no-cache or
just remove both for the new official version. Even could use {{--output-style
compressed}} to get compressed css for production instantly.
This applies to all of the console tools, in most cases would be nice to be
able configure those, but sometimes its inevitable.
> Command line calls should be configurable
> -----------------------------------------
>
> Key: NETBEANS-2145
> URL: https://issues.apache.org/jira/browse/NETBEANS-2145
> Project: NetBeans
> Issue Type: Improvement
> Components: ide - Code
> Affects Versions: 11.0
> Reporter: Iván Barták
> Priority: Major
>
>
> There is a number of issues addressing the same thing here, that external
> tools are changing, and the calls are harcoded in Netbeans. For example:
> * ruby-sass will be officially unmaintained as of 26 March 2019. --no-cache
> is not a paramtere anymore
> * nodeJs debugging not working for the same very reason.
> It would be awsome to be able to fix this between releases, and also fine
> tune those commands. It would be a great relief in a lot of situations.
> Jetbreans does a similar thing, but I like the project configuration by far
> here.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
