Security News
Fluent Assertions Faces Backlash After Abandoning Open Source Licensing
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Compiles Embedded CoffeeScript templates (.eco
) into JavaScript functions.
This plugin requires Grunt >=0.4.0
If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:
npm install grunt-eco --save-dev
Once the plugin has been installed, it may be enabled inside your Gruntfile.js
with this line of JavaScript:
grunt.loadNpmTasks('grunt-eco');
This plugin was designed to work with Grunt 0.4.x and Grunt 1.x. If you're still using grunt v0.3.x it's strongly recommended that you upgrade, but in case you can't please use v0.3.1.
Run this task with the grunt eco
command.
Task targets, files and options may be specified according to the grunt Configuring tasks guide.
Type: Boolean
Default: false
Defines if compiled function will be wrapped in AMD define
function.
Type: String
Default: empty
Defines substing which gets removed from JSTpath of output template.
Type: Boolean
Default: true
Defines if task will warn about empty files on console.
Type: Boolean
Default: true
Defines if compiled function is prepended by code checking/defining presence of JST
object on window
.
please note when amd
is set to true
the jstGlobalCheck
is ignored.
preserve_dirs
and base_path
options are not supported anymore! See examples how task's paths are configured now.
Two most common ways of compiling all globbed paths into single file:
eco: {
app: {
files: {
'path/to/templates.js': ['src/templates/**/*.eco']
}
}
}
eco: {
app: {
src: ['src/templates/**/*.eco'],
dest: 'path/to/templates.js'
}
}
If you need to compile .eco
templates into individual files in some sort of destination folder, you can dynamiccally build path object:
eco: {
app: {
files: [{
expand: true,
src: ['src/templates/**/*.eco'],
dest: 'path/to/templates',
ext: '.js'
}]
}
}
If you ommit dest
key, templates will be compiled right next to your .eco
files.
To configure eco
task simply define options
object:
eco: {
app: {
options: {
amd: true
}
files: {
'path/to/templates.js': ['src/templates/**/*.eco']
}
}
}
This grunt plugin is based on and heavily inspired by grunt-contrib-stylus.
To start, just clone project and then run npm install
in project root.
In lieu of a formal styleguide, take care to maintain the existing coding style. Add unit tests for any new or changed functionality. Always lint and test your code by running grunt
in project's root.
Create new GIT branch (git checkout -b my_feature
) when sending pull request.
Jun 06, 2016 v0.1.3
- Grunt 1.0 compatibilityJun 20, 2014 v0.1.2
- Bubble up task failureJun 16, 2013 v0.1.0
- Refactoring, tests, AMD supportMar 04, 2013 v0.0.2
- Grunt 0.4 compatibilityNov 18, 2012 v0.0.1
- Initial commitCopyright (c) 2012 Gregor Martynus Licensed under the MIT license.
FAQs
Compiles embedded CoffeeScript templates
The npm package grunt-eco receives a total of 9 weekly downloads. As such, grunt-eco popularity was classified as not popular.
We found that grunt-eco demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Fluent Assertions is facing backlash after dropping the Apache license for a commercial model, leaving users blindsided and questioning contributor rights.
Research
Security News
Socket researchers uncover the risks of a malicious Python package targeting Discord developers.
Security News
The UK is proposing a bold ban on ransomware payments by public entities to disrupt cybercrime, protect critical services, and lead global cybersecurity efforts.