Re: [Gmod-ajax] text-index problem

[Ke J. <bio...@gm...>]

Thanks, Colin! I’ll give upgrading node.js a try and report back how it
works.

On Wed, Dec 6, 2023 at 6:12 PM Colin <col...@gm...> wrote:

> Sorry there was a typo in the last email, I meant to say node 14 and 16
> are end of life, 18 is not, so upgrading to 18 or 20 is safe (those are the
> current "LTS" versions)
>
> -Colin
>
> On Wed, Dec 6, 2023 at 7:11 PM Colin <col...@gm...> wrote:
>
>> Hi there,
>> It looks like replaceAll was added in nodejs 15. If you run node
>> --version you can check which version you have. I would imagine that
>> upgrading could help if e.g. you are node 14 (both node 16 and node 18 are
>> now officially "end of life" so it is good to stay updated if possible)
>>
>> We can probably do a better job in our CLI trying to report errors with
>> this. We can maybe also even consider trying to support older node or at
>> least not using bleeding edge features all the time, as I know it is kind
>> of tricky to stay updated
>>
>> -Colin
>>
>> On Wed, Dec 6, 2023 at 3:52 PM Ke Jiang <bio...@gm...> wrote:
>>
>>> Hi,
>>>
>>> I tried to rebuild some indice with new tracks added, but experienced
>>> the following error message:
>>>
>>> UnhandledPromiseRejectionWarning: TypeError:
>>> JSON.stringify(...).replaceAll is not a function
>>>
>>> Even after cleaning up the old indice JSON chunk, I keep having this
>>> error with "text-index" with all new tracks. Based on some searches, it
>>> looks like this is caused by an older version of node.js. Does anyone have
>>> similar problems? If so, does upgrading the node.js solve it? I'm on
>>> JBrowse2 2.8.0.
>>>
>>> Thanks!
>>>
>>> Ke
>>>
>>> _______________________________________________
>>> Gmod-ajax mailing list
>>> Gmo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/gmod-ajax
>>>
>>