Jussi Vatjus-Anttila

I just realised that project contains already travis config - so it's [easy to add node@12 test job there](https://github.com/jupe/stf/commit/94ea8fecd89a82b4dfed9228cf2b6cd0cb491371). There seems to be a [lot of eslint warnings](https://travis-ci.org/jupe/stf/jobs/653803266) - maybe...

761af142 fixes 60 eslint warnings -->

@Mdann52 I merged your changes to [my branch](https://github.com/jupe/stf/tree/node12_with_ci)... I get existing CI pipe to [pass](https://travis-ci.org/jupe/stf/builds/653906768) but stf doesn't work still -> false positive result.. perhaps some gulp configuration issue or...

@Mdann52 could you check gulp config once more time since I think there is still some issues because I get errors because modules can't be resolved like this: ``` Module...

I managed to build and pass backend tests already with node12. Now trying to activate rest of tests to CI that was not part of CI pipeline before. All testing...

@dependabot rebase

@dependabot recreate

Looks a clear bug. probably there is no proper handling when class definition is empy. What happens if you add more content to class? Does example work for you? I’m...

so it didn’t work with node v12 but works with node v10 ? I don’t think that OS causes this..

note that CI doesn’t validate currently node v12.. have to add it there as well