Skip to content

Conversation

@haslersn
Copy link

Inspired by: prometheus/prometheus#8733

I successfully built this commit using the docker images:

  • node:16.13.2-stretch
  • node:16.13.2-buster
  • node:16.13.2-bullseye
  • node:16.13.2-alpine3.14
  • node:16.13.2-alpine3.15
  • node:17.3.1-stretch
  • node:17.3.1-buster
  • node:17.3.1-bullseye
  • node:17.3.1-alpine3.14
  • node:17.3.1-alpine3.15

Note that building in any node:17 image requires NODE_OPTIONS=--openssl-legacy-provider during npm install.

Inspired by: prometheus/prometheus#8733

I successfully built this commit using the docker images:

- node:16.13.2-stretch
- node:16.13.2-buster
- node:16.13.2-bullseye
- node:16.13.2-alpine3.14
- node:16.13.2-alpine3.15
- node:17.3.1-stretch
- node:17.3.1-buster
- node:17.3.1-bullseye
- node:17.3.1-alpine3.14
- node:17.3.1-alpine3.15

Note that building in any `node:17` image requires
`NODE_OPTIONS=--openssl-legacy-provider` during `npm install`.
@noltedennis
Copy link

Thanks for the hint. I just stumbled upon the very same issue. However, with this merge request alone the SASS themes do not compile properly, at least on my end. This seems to be due to a mixup of SCSS and SASS syntaxes in the themes.
I needed to execute the following two substitutions to also build the SASS themes properly:
sed -i "s/!default/!default;/g" themes/MetroMumbleLight/.scss
sed -i "s/!default/!default;/g" themes/MetroMumbleDark/
.scss

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants