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

fix: incorrect output memory file path #225

Merged
merged 1 commit into from
Jan 16, 2019
Merged

fix: incorrect output memory file path #225

merged 1 commit into from
Jan 16, 2019

Conversation

axetroy
Copy link
Contributor

@axetroy axetroy commented Jan 16, 2019

No description provided.

@codecov-io
Copy link

Codecov Report

Merging #225 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@          Coverage Diff          @@
##           master   #225   +/-   ##
=====================================
  Coverage      70%    70%           
=====================================
  Files          13     13           
  Lines         670    670           
=====================================
  Hits          469    469           
  Misses        201    201
Impacted Files Coverage Δ
src/index.js 72.09% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8f8a821...ba67913. Read the comment docs.

Copy link
Contributor

@guybedford guybedford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I was sure I'd fixed this already but turns out it is in the unmerged PR https://github.com/zeit/ncc/pull/112/files#diff-1fdf421c05c1140f6d71444ea2b27638R306!

@rauchg rauchg merged commit 5b54d32 into vercel:master Jan 16, 2019
@rauchg
Copy link
Member

rauchg commented Jan 16, 2019

@guybedford is the v8 one ready?

@guybedford
Copy link
Contributor

@rauchg yes the approach works 100%, and is as good as it will ever be (despite the ugliness!).

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.

4 participants