-
Notifications
You must be signed in to change notification settings - Fork 458
Testing #40
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
Comments
@tunnckoCore maybe we can just drop Babel and switch from The tests aren't async (and likely don't ever need to be), so bublé should be enough for them. |
edit: damn me, didn't clicked the example link. So yea, we can move to it. |
@developit, actually no, we can just use If we change them to use require()s, we totally can just use plain node. We don't have strong need to be ES6. |
Buble and switching to requires seems decent enough. |
if we switch to requires not make sense to use buble et al since we run tests only on node 6 |
true, node 6 has arrow functions right? that's all I cared about |
Yea, exactly. So we can just switch to |
I'm not against that, if you're up for it. Nice to drop the babel dep given it was only for testing. or you know, we write a 500b test framework |
cool, i'll do that in a free time.
haha, yea. actually pretty easy idea btw, for around mid 2017 or early 2018 when everything is ES6 (or at least node v4). also i'm working on minimal framework too ;p |
wondering if rollup (or something) could be used to speed things up (for a tiny test fw) |
yeap, the cli of that small fw would run through rollup ;p thats on my todo and is in process :)) edit: actually mentioned rolldown project, so presets and plus import/export support included. kinda how ava works under the hood |
@developit , @tunnckoCore , I think this issue is no longer relevant and can be closed ? |
Isn't just enough to not use babel and etc? Why we need this and ES6 syntax and imports at all. It is just overhead. With that we can just remove babel from deps and they will look more clean.
/cc @developit
The text was updated successfully, but these errors were encountered: