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

Publish runnable tests & browser data to npm #711

Open
RReverser opened this Issue Dec 22, 2015 · 9 comments

Comments

Projects
None yet
5 participants
@RReverser

See previous discussion at https://twitter.com/kangax/status/678916594089795584.

It would be useful to be able to npm install compat-table and run tests locally in given Node.js engine or bundle into browser. Also, it would be great to have always-fresh officially maintained feature support data (which requires just setting automatic npm-publish on compat-table release).

@ljharb

This comment has been minimized.

Show comment
Hide comment
@ljharb

ljharb Dec 22, 2015

Collaborator

If you want to run tests in node though, you'd want to run the test262 tests since those are the official metric, and are much more thorough than what the compat-table has.

It would be great to have the tests browserifiable tho.

Collaborator

ljharb commented Dec 22, 2015

If you want to run tests in node though, you'd want to run the test262 tests since those are the official metric, and are much more thorough than what the compat-table has.

It would be great to have the tests browserifiable tho.

@RReverser

This comment has been minimized.

Show comment
Hide comment
@RReverser

RReverser Dec 22, 2015

@ljharb Well test262 as you said is much more thorough and what I want is just quick-and-dirty checks that wouldn't slow down initialization.

@ljharb Well test262 as you said is much more thorough and what I want is just quick-and-dirty checks that wouldn't slow down initialization.

@chicoxyzzy

This comment has been minimized.

Show comment
Hide comment
@chicoxyzzy

chicoxyzzy Sep 21, 2016

Collaborator

Closing this in favour of #785 to keep all discussions in a single place

Collaborator

chicoxyzzy commented Sep 21, 2016

Closing this in favour of #785 to keep all discussions in a single place

@chicoxyzzy chicoxyzzy closed this Sep 21, 2016

@RReverser

This comment has been minimized.

Show comment
Hide comment
@RReverser

RReverser Sep 21, 2016

@chicoxyzzy Usually it's the duplicate (that is, newest) issue that gets closed in favor of previous discussion :P

@chicoxyzzy Usually it's the duplicate (that is, newest) issue that gets closed in favor of previous discussion :P

@chicoxyzzy

This comment has been minimized.

Show comment
Hide comment
@chicoxyzzy

chicoxyzzy Sep 21, 2016

Collaborator

@RReverser sorry for that. I'll reopen this issue

Collaborator

chicoxyzzy commented Sep 21, 2016

@RReverser sorry for that. I'll reopen this issue

@chicoxyzzy chicoxyzzy reopened this Sep 21, 2016

@chicoxyzzy

This comment has been minimized.

Show comment
Hide comment
@chicoxyzzy

chicoxyzzy Sep 24, 2016

Collaborator

Babel team started to implement their babel-preset-env and they want to use data from compat-table babel/babel-preset-env#7. I want to help them. Next week I'll create PR with merging browsers definitions data into one module. That can help us to split test results and test runner easier.

Collaborator

chicoxyzzy commented Sep 24, 2016

Babel team started to implement their babel-preset-env and they want to use data from compat-table babel/babel-preset-env#7. I want to help them. Next week I'll create PR with merging browsers definitions data into one module. That can help us to split test results and test runner easier.

@doingweb

This comment has been minimized.

Show comment
Hide comment
@doingweb

doingweb Nov 6, 2016

+1 to a separate npm package for data! My use case is that I'm interested in building a list of features available in a given set of browsers and Node versions.

doingweb commented Nov 6, 2016

+1 to a separate npm package for data! My use case is that I'm interested in building a list of features available in a given set of browsers and Node versions.

@jgardella

This comment has been minimized.

Show comment
Hide comment
@jgardella

jgardella Nov 15, 2016

This would definitely be helpful. I'm currently manually building a JSON file with the info I need from compat-table in my app, which is prone to breaking when certain changes are made to compat-table. A separate npm package for the data, or even just a single JSON file with all the data in this repo, would be great.

This would definitely be helpful. I'm currently manually building a JSON file with the info I need from compat-table in my app, which is prone to breaking when certain changes are made to compat-table. A separate npm package for the data, or even just a single JSON file with all the data in this repo, would be great.

@chicoxyzzy

This comment has been minimized.

Show comment
Hide comment
@chicoxyzzy

chicoxyzzy Nov 16, 2016

Collaborator

@jgardella we are currently moving in that direction

Collaborator

chicoxyzzy commented Nov 16, 2016

@jgardella we are currently moving in that direction

This was referenced Nov 21, 2016

@chicoxyzzy chicoxyzzy referenced this issue Dec 7, 2016

Merged

WIP Post #1014

6 of 6 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment