vsivsi/meteor-file-collection

Upgrade to CoffeeScript 2.0 for latest Meteor compatibility (1.6.1)

Open

#171 opened on Feb 2, 2018

View on GitHub
 (8 comments) (0 reactions) (0 assignees)CoffeeScript (38 forks)github user discovery
help wanted

Repository metrics

Stars
 (158 stars)
PR merge metrics
 (PR metrics pending)

Description

So it looks like the upgrade of the coffeescript from 1.0.17 to 1.12.3_1 after version 1.3.5 of this project has created an incompatibility with the latest Meteor (1.6.1). From what I can tell Meteor 1.6.1 uses a version of babel that is incompatible with this 1.12.3_1 version coffeescript. There is probably two options here:

  • Upgrade this project to use a newer Meteor/Babel compatible version of coffeescript (like a 2.0 version). This seems hard since there are some breaking changes with moving from coffeescript 1.x to 2.0.
  • Downgrade this project back to the last Meteor compatible coffeescript version (1.0.17).

I attempted the first option and ran into problems with your use of super that is now deprecated in coffeescript 2.0.

I ended up falling back to an older coffeescript ... 1.0.17 (the one you use in version 1.3.5) and things seem to be working for now.

Contributor guide

Research direction
Examine the CoffeeScript 2.0 breaking changes, especially the deprecation of super , and replace them with the new syntax (e.g., super). Update the package compatibility with Meteor 1.6.1's Babel.
Tech stack
javascript
Domain
backend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
CoffeeScriptMeteor
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60