Is this due to Jasmine being unable to read es6, perhaps? @sagarpreet-chadha @Shulammite-Aso @shreyaa-sharmaa @NitinBhasneria @keshav234156 - any thoughts? I notice that we added Terser to woofmark in the meantime?

Actually it's difficult to find as we are able to find only when we integrate it with Editor. It's due to an update that we have made in woofmark and it doesn't get noticed when we test them separatly
@jywarren Do you know any way we can test this?

I'm not sure ... the fact that Jasmine is not finding it at all seems to be a big hint. And yet it passes Jest tests.

We haven't really changed the Jasmine setup, i think? https://github.com/publiclab/PublicLab.Editor/tree/main/spec/javascripts (one change 18 days ago)

This to me suggests that it's a difference in the environment somehow. I know Jasmine has trouble with ES6 and we don't have Babel installed to deal with this... ?

Also noting connection to a previous issue with Travis here which ended up being related to Node version: #439 - and there, we asked @HarshKhandeparkar and @VladimirMikulic for help. If we get really stuck let's see if they have suggestions, as they are really good at this stuff?

Thanks!

I agree with @jywarren , it maybe due to es6 usage in upstream library - woofmark.
I saw that we are now telling jshint that the code is written in es6 here:
https://github.com/jywarren/woofmark/blob/39237b798308e6855acde1a938c18a8e4da62fce/.jshintrc#L2

Maybe this is causing issue?

I think it is due to use of const keyword which is es6 construct (I only asked asked people to change var to const in some PR's)

We are using const and even let also here jywarren/woofmark@e6f56ea

@Shulammite-Aso would you like to test if this is the issue?

There are 2 things we can do now in woofmark:

1. Remove let and const everywhere and then try installing this branch in PL.editor by changing package.json (linking woofmark to your branch) and then running Jasmine tests locally.

2. Setup a transpiler like babel which will first convert ES6 to lower ECMA version and then later bundle them into /dist folder. (This we should do anyways)

Thanks 😄

Awesome. I guess I feel like option 2 makes sense, but it is a bit of work. @sagarpreet-chadha has actually done this (although i didn't review it 😭 ) in this PR so you can see how it's usually configured!

https://github.com/publiclab/leaflet-environmental-layers/pull/240/files

Hi @sagarpreet-chadha @jywarren is anybody working on this yet?
Things must have gotten over my head. I thought i read you were working on this @sagarpreet-chadha ?
Just reading through again and saw that wasn't what you said.

I should try setting this up if nobody is already on it, and hit you up @sagarpreet-chadha if i have any question.

Thank you so much! we had gotten a little behind on this but your help is SO APPRECIATED. This is a big blocker! Looking at your solution now. Thanks!! 🎉