Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for script pre-processing via shebang/#! #45

Merged
merged 1 commit into from
Nov 19, 2015

Conversation

shayne
Copy link
Contributor

@shayne shayne commented Oct 29, 2015

This pull request adds support for generic pre-preprocessing of
JavaScript through the use of a shebang at the top of your Phoenix JS
config.

This also adds support for ~/.phoenix[-debug].js being a symlink

Example:

#!/usr/bin/env babel
// ... Custom Phoenix JS

This pull request adds support for generic pre-preprocessing of
JavaScript through the use of a shebang at the top of your Phoenix JS
config.

This also adds support for ~/.phoenix[-debug].js being a symlink

**Example:**
```javascript
\#!/usr/bin/env babel
// ... Custom Phoenix JS
```
@kasper kasper merged commit 6d6f7bd into kasper:2.0 Nov 19, 2015
kasper added a commit that referenced this pull request Nov 19, 2015
kasper added a commit that referenced this pull request Nov 19, 2015
kasper added a commit that referenced this pull request Nov 19, 2015
@shayne shayne deleted the 2.0-shebang branch November 19, 2015 17:38
@kasper kasper added this to the 2.0 milestone Nov 19, 2015
@kasper kasper self-assigned this Nov 19, 2015
@kasper
Copy link
Owner

kasper commented Nov 19, 2015

@shayne Thank you ever so much for this great idea and pull request! I tested it out and made some small alterations to make it more robust. It is now merged.

*errorMessage = [[NSString alloc] initWithData:errorData encoding:NSUTF8StringEncoding];
}

/* Read past the shebang line to prevent syntax error */
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #46 please explain which preprocessors leave the shebang in their output? None I think.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants