Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can’t:form #1

Open
wants to merge 57 commits into
base: master
Choose a base branch
from
Open

Conversation

usernamealreadyis
Copy link

Can’t automatically merge. Don’t worry, you can still create the pull request.

klamping and others added 30 commits September 4, 2012 20:05
Trying to fix the two issues noted in Pull Request felixge#8
(felixge#8) so that
coffee-script support can be added.
Fork of CoffeeScript support Pull Request (felixge#8)
You need to `require('coffee-script')` before requiring CoffeeScript modules.
It didn't even work, according to the tests.
It is the name of my diety's arch-rival, and a Forbidden Word in my religion.
- Move CoffeeScript to devDependencies.
- Remove engines field.
- Add bugs, keywords, and license fields.
* For fear that glboal.$$cov... might be present w/o
istanbul, I wrapped the istanbul interceptor in a big
try catch

* To prevent the finding coffeescript.compile and
istanbul instrumentSync on every single file, I 
cache them.
Presumably this will be appropriate for any future
built-in source transformers added to the project.
Implements Istanbul coverage support and user-defined sourceTransformers
These days you need to run the .register() function.
Use both the '$$cov_*' and istanbul's default '__coverage__' var to see if istanbul is running
domenic and others added 27 commits June 10, 2014 22:08
Istanbul, a dev dependency, uses util.deprecate, which doesn't work there.
It was doing element-wise copy, but it should just be assigning the exports.
It is generated via much hackery, but then checked in for a given release, to avoid how this seems way too fragile to do at runtime.

Fixes felixge#33. Inspired greatly by @robrich's work in felixge#34.
It'll still work, but the tests fail, and also nobody should be using something that old.
Sources ending with an end-of-line comment (not followed by a newline character) aren't wrapped properly. The second part of the wrapper is treated as part of the comment in such a case. Adding a newline character in fixes this issue.
Add docs; clarify tests; use `undefined` to signal default, not falsy.
Since the node.js is now in strict mode we can't get into it with `caller`. However we can use more straightforward hacks.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

10 participants