This may not be our responsibility, but we are depending on jade@>=0.25.0. However, recent major releases (~1.x.x) have introduced some issues with consistency across my team's workstations (as new developers are brought on).
Specifically, some are getting exceptions thrown for using deprecated syntax (yeah - not a warning - an error...).
This piece is of course the user's responsibility to conform to the proper syntax of Jade, however, in an effort to reduce possible confusion between different installations holding different versions of Jade, I think that we should narrow the version range in the package file.
Now that Jade is recently at 1.0.x (12 days ago), it's probably best to update the dependency anyway.
jnordberg
commented
10 years ago
This may not be our responsibility, but we are depending on
jade@>=0.25.0. However, recent major releases (~1.x.x) have introduced some issues with consistency across my team's workstations (as new developers are brought on).Specifically, some are getting exceptions thrown for using deprecated syntax (yeah - not a warning - an error...).
This piece is of course the user's responsibility to conform to the proper syntax of Jade, however, in an effort to reduce possible confusion between different installations holding different versions of Jade, I think that we should narrow the version range in the package file.
Now that Jade is recently at
1.0.x(12 days ago), it's probably best to update the dependency anyway.