Skip to content

Bad versionsing of dependencies in package.json #1

@brettcave

Description

@brettcave

If a version is not specified in package.json of customer.io (specifically the "coffee-script" dependency), then the latest available version will be used.

Coffee-script 1.7.1 has been published to NPM, and this is breaking customer.io 0.0.2. Previously, coffee-script 1.6.3 was being used, and worked. The error is found when requiring customer.io:

 Error: Cannot find module './src'
   at Function.Module._resolveFilename (module.js:338:15)
   at Function.Module._load (module.js:280:25)
   at Module.require (module.js:364:17)
   at require (module.js:380:17)
   at Object.<anonymous> (/project/node_modules/customer.io/index.js:2:18)

By locking down the major dependency version in package.json, API changes in major dependency releases will not break customer.io. Use the following in package.json:

"coffee-script" : "1.6.x"

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions