Skip to content

Some filters won't work with wrapper scripts #50

@berarma

Description

@berarma

I guess this could be an enhancement and make things easier for people using tools like nodenv to manage nodejs versions.

I've found this issue while using the Uglifyjs filter but the CoffeeScript filter does the exact same thing.

These filters call nodejs passing a file from /usr/local/bin. We're guessing the file in the bin directory isn't executable by itself (while it should) and that it will be the Javascript file, not some wrapper around it. In my case, I have links to the nodenv shims and thus the filter fails.

I think the best fix would be changing the configuration seetings so that I could just point to an executable without caring about nodejs versions and paths when I don't need it.

I could accomplish this using this config:

'node' => '/usr/local/bin/uglifyjs'
'uglify' => ''

But this could read easier as:

'uglify' => /usr/local/bin/uglifyjs'

And make it the default configuration since it should work in most cases I guess. The node and node_path settings should be seldom needed.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions