Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G gulp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 24
    • Issues 24
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gulp
  • gulp
  • Issues
  • #103
Closed
Open
Issue created Jan 07, 2014 by Administrator@rootContributor

Using coffee-script for gulpfile will break with the next release of CS

Created by: xixixao

With the next release of CS, requiring coffee-script won't autoregister .coffee extensions. Instead, requiring coffee-script/register will be required.

This can be fixed by changing the README when the time comes, but I'd opt for a different solution, that would allow .coffee config without having to specify the registration every time (short of an alias).

See https://github.com/jashkenas/coffee-script/pull/3279

Assignee
Assign to
Time tracking