29
100%
master: 100%

Ran 29 Jul 2016 03:34AM UTC

Jobs 1

Files 1

Run time 0s

Badge

Embed ▾

pending completion

Build # 29

Build Type

push

travis-ci

Committed by

Yeti-or

Commit Message

Add empty object to expressionStatements.

The idea is next: when you write
```
module.export = {
    42: 42
}
```

You assume that you are in node env, so you have global object module,
but we as you see in this code it doesn't exports anything because of typo.
`export` -> `exports`
so in node env you will get undefined
but as we want to be nice eval and eval expressions without module.exports:
```
({ 42: 42 })
```
we try to do it and get an Error, because code have no `module` to write `export` prop in it
So our desicion is to temporaly polute global object with `module`.

Run Details

47 of 50 relevant lines covered (94.0%)

7.66 hits per line

Jobs

ID	Job ID	Ran	Files	Coverage
2	29.2 (COVERALLS=1)	29 Jul 2016 03:34AM UTC	0	94.0	Travis Job 29.2

Source Files on build 29

Detailed source file information is not available for this build.

nodules / node-eval / 29
100%
master: 100%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 29

nodules / node-eval / 29 100% master: 100%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 29

nodules / node-eval / 29
100%
master: 100%

README BADGES
x