You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 5, 2021. It is now read-only.
Just trying this in place of truffle and while compile seems to go fine my tests fall over on something like:
import expectThrow from '../helpers/expectThrow';
In truffle the way to allow this syntax is with @babel dependencies added to the package.json and a .babelrc file and the below to the truffle-config.js to activate:
I'm no longer working on this, but I think if you want to boost popularity of your framework and help teams migrate who already have a large bank of tests (for eg. I know we had close to 500) you might want to consider looking at this some more.
What the tests do is kind of immaterial, the bug is in the import yes...it's an es6 vs es5 problem your framework currently doesn't have a way to support es6 style code but truffle does. This is the problem.
The code is taken from a truffle "box" as mentioned, it's their code so they would be best asked why they put a .sol in the test. That doesn't affect the bug though.
I went through your guide while I was looking at this and it looks reasonably simple to move over...unless you use es6 code in your bank of truffle tests.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just trying this in place of truffle and while compile seems to go fine my tests fall over on something like:
import expectThrow from '../helpers/expectThrow';
In truffle the way to allow this syntax is with @babel dependencies added to the package.json and a .babelrc file and the below to the truffle-config.js to activate:
How can I do the same with etherlime?
Thanks.
The text was updated successfully, but these errors were encountered: