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

Update sanctuary-scripts to version 3.x #13

Merged
merged 1 commit into from
Apr 5, 2019
Merged

Update sanctuary-scripts to version 3.x #13

merged 1 commit into from
Apr 5, 2019

Conversation

Avaq
Copy link
Contributor

@Avaq Avaq commented Mar 22, 2019

Motivation

To keep dependencies up to date and close #12

Changes

  • opening-delimiter option added to configure what sanctuary-scripts sees as code blocks
  • scripts/test could be removed because sanctuary-scripts supports mjs files now

@Avaq Avaq self-assigned this Mar 22, 2019
@Avaq Avaq requested a review from paolobueno March 22, 2019 09:17
@Avaq Avaq force-pushed the avaq/scripts branch 2 times, most recently from edb550a to cc9ba40 Compare March 22, 2019 09:29
@Avaq
Copy link
Contributor Author

Avaq commented Mar 22, 2019

Grrr. Coveralls is being an 🥚 again

@Avaq
Copy link
Contributor Author

Avaq commented Mar 22, 2019

This is what's happening in the build-server. I don't yet understand why.

$ npm run coverage
> react-collect@1.0.3 coverage /home/travis/build/wearereasonablepeople/react-collect
> nyc report --reporter=text-lcov | coveralls
[error] "2019-03-22T09:49:40.232Z"  'error from lcovParse: ' 'Failed to parse string'
[error] "2019-03-22T09:49:40.234Z"  'input: ' ''
[error] "2019-03-22T09:49:40.234Z"  'error from convertLcovToCoveralls'
/home/travis/build/wearereasonablepeople/react-collect/node_modules/coveralls/bin/coveralls.js:18
        throw err;
        ^
Failed to parse string

@Avaq
Copy link
Contributor Author

Avaq commented Mar 22, 2019

Found the related issue: nickmerwin/node-coveralls#207

@Avaq
Copy link
Contributor Author

Avaq commented Mar 22, 2019

That leads to a bug in node v11; but we've been using v10 all this time.

@Avaq
Copy link
Contributor Author

Avaq commented Mar 22, 2019

It doesn't work on any of the node versions I've tried:

  • 10.15.x
  • 10.15.0
  • 10.14.x
  • 10.14.0
  • 11.x

It doesn't work with any of the nyc versions I've tried:

  • 13.3.0
  • 13.2.x
  • 13.2.0

It doesn't work with any of the coveralls versions I've tried:

  • 3.0.2
  • 3.0.0

@Avaq Avaq force-pushed the avaq/scripts branch 2 times, most recently from d971e4e to 381b57e Compare March 22, 2019 10:21
@Avaq
Copy link
Contributor Author

Avaq commented Apr 5, 2019

@paolobueno checks passed! :)

@Avaq Avaq merged commit c146768 into master Apr 5, 2019
@Avaq Avaq deleted the avaq/scripts branch April 5, 2019 15:38
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.

None yet

2 participants