Upgrade codemirror and lezer to the latest version

[Nexucis]

No description provided.

[Nexucis]

build is failing because of the warnings :/

[roidelapluie]

Do you think so? 243 seems to indicate a permission denied issue, which is caused by trying to crate /.npm

[Nexucis]

ah I was looking at the tests jobs where the warning was the root cause.

But yeah the build job is still failing which is weird. I mean concerning the UI, it is doing the same thing than the job ui_test.

[Nexucis]

How do you know it is trying to create a folder .npm @roidelapluie ? And why does it work in other jobs ?

[MrDeerly]

Looks good for me. Just make sure to bump lezer-promql in codemirror-promql (not sure if that's done in an automated way)

[Nexucis]

yeah it's done automatically @MrDeerly. It's a npm workspace, so codemirror-promql is currently using the local version of lezer-promql.

[Nexucis]

By looking at #10840, it doesn't look like the build failure is related to this PR actually. It looks like it's a general issue actually :/

[juliusv]

What's the reason behind this unsetting of the CI variable?

[Nexucis]

it's because there are some warnings raised coming from some dependencies in node-modules. I didn't find other way to ignore them than like that.
Like that warnings are not treated as errors

[juliusv]

👍 Don't super like the CI="" part, but it seems like everyone is just doing that :/

[MrDeerly]

@Nexucis with this change the lezer-promql isn't installed in codemirror-promql anymore as a dependency. Probable codemirror-promql was published and build before lezer-promql?

Contents of /node_modules/@prometheus-io/codemirror-promql/node_modules:

lru-cache

^ #11017

[Nexucis]

@MrDeerly it should be installed in @promethus-io folder, since it is now published as @prometheus-io/lezer-promql