Git Product home page Git Product logo

grunt-csso's People

Contributors

ahomu avatar havenchyk avatar mrhyde avatar nitriques avatar restlessdesign avatar sapegin avatar t32k avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

grunt-csso's Issues

Grunt 0.4 Release

I'm posting this issue to let you know that we will be publishing Grunt 0.4 on Monday, February 18th.

If your plugin is not already Grunt 0.4 compatible, would you please consider updating it? For an overview of what's changed, please see our migration guide.

If you'd like to develop against the final version of Grunt before Monday, please specify "grunt": "0.4.0rc8" as a devDependency in your project. After Monday's release, you'll be able to use "grunt": "~0.4.0" to actually publish your plugin. If you depend on any plugins from the grunt-contrib series, please see our list of release candidates for compatible versions. All of these will be updated to final status when Grunt 0.4 is published.

Also, in an effort to reduce duplication of effort and fragmentation in the developer community, could you review the grunt-contrib series of plugins to see if any of your functionality overlaps significantly with them? Grunt-contrib is community maintained with 40+ contributors—we'd love to discuss any additions you'd like to make.

Finally, we're working on a new task format that doesn't depend on Grunt: it's called node-task. Once this is complete, there will be one more conversion, and then we'll never ask you to upgrade your plugins to support our changes again. Until that happens, thanks for bearing with us!

If you have any questions about how to proceed, please respond here, or join us in #grunt on irc.freenode.net.

Thanks, we really appreciate your work!

Fatal error: Identifier is expected (958)

Package version: 2.2.0

Affected node versions: 8.1.4

My grunt-csso task fails with the error Fatal error: Identifier is expected (958).

package.json
gruntfile.js

grunt-csso and grunt-cli are installed locally.

I've taken these steps in my project.

rm -rf node_modules
npm i -D grunt-cli
npm i -D grunt-csso
npm i for the other packages
grunt

Running "csso:build" (csso) task
Fatal error: Identifier is expected  (958)

Error thrown on media queries rules concatenation

Hi, I get the warning from shell during grunt watch execution:

Warning: Please check the validity of the CSS block starting from the line #1345 Use --force to continue.

The error reported is this:

1343    @media only screen and (min-width: 768px), only print {
1344        .not-from-tablet-portrait {
1345            display: none !important;
1346        }
1347    ...

I'm not sure what's the problem, maybe this can help you to find out something, I'm sure this is a valid CSS because it's previously generated with grunt-contrib-less.

Dynamic mappings not recreating all the min file

Using dynamic mappings are not rewriting all the content in each file, is adding all the content inside each time I run the command.
I also test the dynamic mappings with one file and the problem persist.

theme: {
        files: [{
            expand: true,     // Enable dynamic expansion.
            cwd: '<%= scaffold.build.assets %>/themes/default',      // Src matches are relative to this path.
            src: ['**/*.css'], // Actual pattern(s) to match.
            dest: '<%= scaffold.build.assets %>/themes/default',   // Destination path prefix.
            ext: '.min.css',   // Dest filepaths will have this extension.
            extDot: 'first'   // Extensions in filenames begin after the first dot
        }]
    }

peerDependencies causes error

Package version: 2.2.0

Affected node versions:
- [x] 6.x

According to this ticket (gruntjs/grunt#1537), your peerDependency to "grunt-cli": ">=1.0.0" create this error message :)

UNMET PEER DEPENDENCY grunt-cli@>=1.0.0
npm WARN [email protected] requires a peer of grunt-cli@>=1.0.0 but none was installed.

PS: Thanks for this grunt plugin, it works awesome!!!

Support for short path syntax

If you want to write optimised output to the same file you have to specify the same path twice. It happens when it’s not a source file and generated by a preprocessor:

csso: {
    task: {
        files: {
            'styles/screen.css': 'styles/screen.css'
        }
    }
},

But in grunt-autoprefixer it’s possible to use src shortcut for such cases:

autoprefixer: {
    task: {
        src: 'styles/screen.css'
    }
}

But when I try to use the notation for grunt-csso, I see following error:

grunt csso
Running "csso:task" (csso) task
Warning: Unable to write "undefined" file (Error code: undefined)

Could you please implement support for the same shortcut? Thank you.

Better error management

It would be cool to display the exception coming from csso.

I would change the following

var proceed = csso.minify(original, { restructuring: options.restructuring, debug: options.debug });

to

var proceed;
try {
    proceed = csso.minify(original, { restructuring: options.restructuring, debug: options.debug });
}
catch (ex) {
   grunt.fail.fatal(ex.message + '  ' + ex.parseError.line);
   return;
}
if (proceed && proceed.length === 0) {

I was getting "Unexpected input" error but I would like to get the actual line where the error occurred.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.