When importing component inside custom element, style is discarded #4662

gnuletik · 2021-09-23T12:47:38Z

Version

3.2.14

Reproduction link

Steps to reproduce

git clone git@github.com:gnuletik/vue-ce-import-comp-style.git
cd vue-ce-import-comp-style
yarn run dev

Open browser

What is expected?

CSS of OtherComponent.vue should be applied.
The text "It should be blue" should be blue.

What is actually happening?

Style is not applied.

I tried renaming OtherComponent to OtherComponent.ce.vue, but the result is the same.

This is useful when writing a set of custom elements to have shared components between custom elements.

tony19 · 2021-09-27T06:16:16Z

Also encountered this issue. Here's a couple more repros:

raffobaffo · 2021-09-27T13:30:14Z

I also encountered it and just worked on a fix, will create a PR soon (my first one here 😨 )

gnuletik · 2021-09-27T13:33:03Z

I just realized there is already an open PR about this : #4309

raffobaffo · 2021-09-27T15:37:08Z

I see 👁️ . My changes are very similar, just its more recursive, meaning also components at any level are interested.

…ted components. Missing feature, store available styles to avoid dupes. close vuejs#4662

raffobaffo · 2021-09-28T10:32:03Z

Ok, this should be safer now. This addition will add any child component style to the main parent, no matter how deeply nested it is

…ted components. Missing feature, store available styles to avoid dupes. close vuejs#4662

pawel-marciniak · 2021-10-14T12:15:20Z

Anyone know if it will be merged? It blocks me from using Vue 3 :/ @raffobaffo What about third party nested components (e.g. imported from some package)? Will your solution also work for them?

LinusBorg · 2021-10-14T13:40:00Z

We will solve this, it might take a few more days or weeks though.

pawel-marciniak · 2021-10-14T13:43:54Z

We will solve this, it might take a few more days or weeks though.

@LinusBorg Ok, thanks for quick reply, it's good to know that it will be solved at some point in the future :)

raffobaffo · 2021-10-16T15:10:05Z

@pawel-marciniak Yes, it is.
@LinusBorg Great to hear. Atm to overcome this problem, we are using an own extended version of the defineCustomElement that provides that hack I inserted in the pr.

lucasantunes-ciandt · 2021-11-09T23:34:25Z

@raffobaffo would you mind sharing how did you extend it? I tried it here by basically cloning /runtime-dom/src/apiCustomElement.ts with your changes but got a lot of syntax error from TS.

raffobaffo · 2021-11-10T21:38:01Z

@lucasantunes-ciandt sorry but not TS for me on this project. This is pretty much the hack I built:

import { defineCustomElement as rootDefineCustomElement } from 'vue'
[...]
export const getChildrenComponentsStyles = (component) => {
  let componentStyles = [];
  if (component.components) {
    componentStyles = Object.values(component.components).reduce(
      (
        aggregatedStyles,
        nestedComponent,
      ) => {
        if (nestedComponent?.components) {
          aggregatedStyles = [
            ...aggregatedStyles,
            ...getChildrenComponentsStyles(nestedComponent),
          ];
        }
        return nestedComponent.styles
          ? [...aggregatedStyles, ...nestedComponent.styles]
          : aggregatedStyles;
      }, [],
    );
  }
if (component.styles) {
    componentStyles.push(...component.styles);
  }

  return [...new Set(componentStyles)];
};

export const defineCustomElement = (component) => {

  // Attach children styles to main element
  // Should be removed once https://github.com/vuejs/vue-next/pull/4695
  // gets merged
  component.styles = getChildrenComponentsStyles(component);
  const cElement = rootDefineCustomElement(component);

  // Programmatically generate name for component tag
  const componentName = kebabize(component.name.replace(/\.[^/.]+$/, "") );
  // eslint-disable-next-line tree-shaking/no-side-effects-in-initialization
  customElements.define(componentName, cElement);

  // Here we are attaching a <ling ref="style" href="/style.css" ...
  // This is to have the css outside of the shadow dom
  // also available inside the shadow root without inlining them
  // The browser will automatically use the available declaration and won't
  // make multiple calls
  const componentShadowDom = document.querySelector(componentName)?.shadowRoot;
  if(componentShadowDom){
    const styleLink = document.createElement('link');
    styleLink.setAttribute('rel', 'stylesheet');
    styleLink.setAttribute('href', 'style.css');
    componentShadowDom.appendChild(styleLink);
  }
}

lucasantunes-ciandt · 2021-11-11T21:35:21Z

@raffobaffo Thank you so much! I thought you were literally extending the whole file 😅

I tried this code here, but unfortunately it doesn't work. I suppose it expects the components are all custom elements, e.g. Component.ce.vue and ChildComponent.ce.vue.

When my components are named Component.vue they don't come with any styles prop, only when they're Component.ce.vue.

I reckon we'll need to wait for your PR to be merged.

lucasantunes-ciandt · 2021-11-11T22:16:53Z

Oopsie, actually this works! Thank you @raffobaffo!!

I was a bit confused about the meaning of .ce.vue, now I realize the extension is only a Custom Element MODE and not actually declaring those components as custom elements. This means I really should have them as .ce.vue in order for this to work, even after this PR is merged.

So my two cents to the Issue Owner: OtherComponent.vue should be OtherComponent.ce.vue indeed.

lucasantunes-ciandt · 2021-11-11T23:37:47Z

@raffobaffo I had only to change the injection a little bit, since I may have multiple instances of the same Custom Element:

document.querySelectorAll(customElementName).forEach((element) => {
  if (!element.shadowRoot) return;

  const styleLink = document.createElement('link');
  styleLink.setAttribute('rel', 'stylesheet');
  styleLink.setAttribute('href', 'style.css');

  element.shadowRoot.appendChild(styleLink);
});

raffobaffo · 2021-11-12T17:09:05Z

@lucasantunes-ciandt Nice find 👍 ! Still this block is not part of the PR, because this actually make sense to have it in a separate module that is loaded just when custom elements are needed. In my case I have a components library and I want to have 2 exports, one to be consumed by Vue applications and one for browsers/html.
This part would maybe make more sense in some Vite or VueCli plugin 🤔 .

lucasantunes-ciandt · 2021-11-13T03:27:30Z

@raffobaffo Exactly! In our case we're using Vue inside a CMS, so we'll be only exporting custom elements to use within it instead of creating a Vue app, so we'll definitely keep that part because we need some external styles and even scripts from the CMS to be injected into the elements.

adamdehaven · 2021-11-24T17:46:20Z

@raffobaffo would your solution also inject styles into the shadow DOM from child components imported within the defineCustomElement component that originate from external packages?

As an example, if I define and export a component with defineCustomElement, but within that element is a button component that is being imported from an external package (and is not created with defineCustomElement).

Also @lucasantunes-ciandt do you have a working example using the reproduction repo?

raffobaffo · 2021-11-27T14:26:43Z

@adamlewkowicz hard to answer. Depends from how the imported element (third party) is structured. Does it comes with is own inline styles? If yes, it should work, if not, it cant.

adamdehaven · 2021-11-27T14:50:47Z

@raffobaffo would you be willing to update your reproduction repo linked above with a new branch that utilizes your fix? I tried what you have but wasn't able to get it working for some reason. Would be much appreciated!

dezmound · 2021-11-29T13:28:29Z

As a workaround I've created component, which tracks Mutation in document.head and inline style tags (must includes comment /* VueCustomElementChildren */) into shadow dom in dev mode, for production it inlines link for stylesheets:

CustomElements.vue

<script setup lang="ts">
/***
 * @see https://github.com/vuejs/vue-next/issues/4662
 **/

import { computed } from "vue";
import { onMounted, onUnmounted, ref } from "@vue/runtime-core";

const props = defineProps<{
  cssHref?: string;
}>();

const inlineStyles = ref<HTMLElement[]>([]);
const html = computed(() =>
  // @ts-ignore
  import.meta.env.PROD && props.cssHref
    ? `<link href="${props.cssHref}" rel="stylesheet"/>`
    : `<style>${inlineStyles.value
        .map((style) => style.innerHTML)
        .join("")}</style>`
);

const findAndInsertStyle = () => {
  inlineStyles.value = Array.from(
    document.getElementsByTagName("style")
  ).filter((node) => {
    return node.innerHTML.includes("VueCustomElementChildren");
  });
};

// @ts-ignore
if (!import.meta.env.PROD) {
  const observer = new MutationObserver(findAndInsertStyle);
  observer.observe(document.head, {
    childList: true,
    subtree: true,
    characterData: true,
  });

  onMounted(findAndInsertStyle);
  onUnmounted(() => {
    observer.disconnect();
  });
}
</script>

<template>
  <div v-html="html"></div>
</template>

<style>
/* VueCustomElementChildren */
</style>

SomeOtherComponent.vue

<script setup lang="ts">
</script>

<template>
  <div class="some-other">test</div>
</template>

<style>
/* VueCustomElementChildren */
.some-other {
  color: red;
}
</style>

App.ce.vue

<script setup lang="ts">
import CustomElements from "@/components/CustomElements.vue";
import SomeOtherComponent from "@/components/SomeOtherComponent.vue";
</script>

<template>
  <CustomElements css-href="/style/stylesheet.css" />
  <SomeOtherComponent />
</template>

<style>
</style>

Makoehle · 2022-01-19T21:23:19Z

I've found a blog by @ElMassimo describing a workaround which works for me. To summarize:

Name all SFC file names *.ce.vue
In your main.ts use defineCustomElement.
Define your custom elements.
Use tag names instead of importing components. E.G <HelloWorld msg="hi"/> becomes \<hello-world msg="hi" />.

Don't know the limitations yet e.G vuex etc.

claudiomedina · 2022-02-16T09:22:14Z

As a workaround I've created component, which tracks Mutation in document.head and inline style tags (must includes comment /* VueCustomElementChildren */) into shadow dom in dev mode, for production it inlines link for stylesheets:

@dezmound, wont that make other Vue custom elements' styles get injected into the first one?

For example, if you have 3 custom elements in the same page:

element-a is inserted in page adds style to document.head
observer from element-a copies the style from element-a to its shadow DOM
element-b is inserted in page and adds style to document.head
observer from element-a copies the style from element-b to element-a shadow DOM
observer from element-b copies the style from element-a and element-b to element-b shadow DOM
element-c is inserted in page and adds style to document.head
observer from element-a copies the style from element-c to element-a shadow DOM
observer from element-b copies the style from element-c to element-b shadow DOM
observer from element-b copies the style from element-a, element-b and element-c to element-c shadow DOM

As so you end up with unwanted styles from other components into the components. It only works well if there is only one Vue based custom element/application in the page.

dezmound · 2022-02-16T10:53:46Z

As a workaround I've created component, which tracks Mutation in document.head and inline style tags (must includes comment /* VueCustomElementChildren */) into shadow dom in dev mode, for production it inlines link for stylesheets:

@dezmound, wont that make other Vue custom elements' styles get injected into the first one?

For example, if you have 3 custom elements in the same page:

element-a is inserted in page adds style to document.head

observer from element-a copies the style from element-a to its shadow DOM

element-b is inserted in page and adds style to document.head

observer from element-a copies the style from element-b to element-a shadow DOM

observer from element-b copies the style from element-a and element-b to element-b shadow DOM

element-c is inserted in page and adds style to document.head

observer from element-a copies the style from element-c to element-a shadow DOM

observer from element-b copies the style from element-c to element-b shadow DOM

observer from element-b copies the style from element-a, element-b and element-c to element-c shadow DOM

As so you end up with unwanted styles from other components into the components. It only works well if there is only one Vue based custom element/application in the page.

@claudiomedina Thank you for the comment 🙏 That's right, but it can be solved for example with adding scope prop for CustomElements.vue:

CustomElements.vue

<script setup lang="ts">
/***
 * @see https://github.com/vuejs/vue-next/issues/4662
 **/

import { computed } from "vue";
import { onMounted, onUnmounted, ref } from "@vue/runtime-core";

const props = defineProps<{
  cssHref?: string;
  scope?: string;
}>();

const inlineStyles = ref<HTMLElement[]>([]);
const html = computed(() =>
  // @ts-ignore
  import.meta.env.PROD && props.cssHref
    ? `<link href="${props.cssHref}" rel="stylesheet"/>`
    : `<style>${inlineStyles.value
        .map((style) => style.innerHTML)
        .join("")}</style>`
);

const findAndInsertStyle = () => {
  inlineStyles.value = Array.from(
    document.getElementsByTagName("style")
  ).filter((node) => {
    return node.innerHTML.includes(`${props.scope}: VueCustomElementChildren`);
  });
};

// @ts-ignore
if (!import.meta.env.PROD) {
  const observer = new MutationObserver(findAndInsertStyle);
  observer.observe(document.head, {
    childList: true,
    subtree: true,
    characterData: true,
  });

  onMounted(findAndInsertStyle);
  onUnmounted(() => {
    observer.disconnect();
  });
}
</script>

<template>
  <div v-html="html"></div>
</template>

<style>
/* VueCustomElementChildren */
</style>

Element-a.ce.vue

<script setup lang="ts">
import CustomElements from "@/components/CustomElements.vue";
import SomeOtherComponent from "@/components/SomeOtherComponent.vue";
</script>

<template>
  <CustomElements css-href="/style/stylesheet.css" scope="Element A" />
  <SomeOtherComponentForA />
</template>

<style>
</style>

SomeOtherComponentForA.vue

<script setup lang="ts">
</script>

<template>
  <div class="some-other">test</div>
</template>

<style>
/* Element A: VueCustomElementChildren */
.some-other {
  color: red;
}
</style>

Element-b.ce.vue

<script setup lang="ts">
import CustomElements from "@/components/CustomElements.vue";
import SomeOtherComponent from "@/components/SomeOtherComponent.vue";
</script>

<template>
  <CustomElements css-href="/style/stylesheet.css" scope="Element B" />
  <SomeOtherComponentForB />
</template>

<style>
</style>

SomeOtherComponentForB.vue

<script setup lang="ts">
</script>

<template>
  <div class="some-other">test</div>
</template>

<style>
/* Element B: VueCustomElementChildren */
.some-other {
  color: red;
}
</style>

My example's just a solution that allows to write and use components for CustomElement without casting it into native custom elements, so it's still compactable with TS. The child components may be shared with any entry points such as Vue App or different Custom Element. It doesn't contain complex logic because it does not need to. In some other cases as in your example, this workaround may be easily improved.

Danny-Engelman · 2023-05-17T10:17:28Z

Any update, or is it time to ditch Vue and switch to Svelte?

soultice · 2023-05-17T14:41:15Z

Any update, or is it time to ditch Vue and switch to Svelte?

Oddly enough, Svelte has the exact same issue: sveltejs/svelte#4274 where there is talk about switching to Vue.

haoqunjiang · 2023-05-17T14:47:25Z

Should we by any chance expect a fix anytime soon

This issue is labeled as "p4-important".

I can't promise, but in an ideal world, the priority queue could be like this:

Fixing v3.3 regressions
p4 issues in core / important issues in other core repos / other planned 3.4 features
p3 issues
…

baiwusanyu-c · 2023-05-18T06:50:22Z

Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it too, you can use this plugin
https://github.com/baiwusanyu-c/unplugin-vue-ce/blob/master/packages/sub-style/README.md

mrcego · 2023-05-18T23:08:48Z

Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it too, you can use this plugin
https://github.com/baiwusanyu-c/unplugin-vue-ce/blob/master/packages/sub-style/README.md

Could I using regular Vue components with scoped styles tag inside custom elements?

baiwusanyu-c · 2023-05-19T01:13:13Z

Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it too, you can use this plugin
https://github.com/baiwusanyu-c/unplugin-vue-ce/blob/master/packages/sub-style/README.md

Could I using regular Vue components with scoped styles tag inside custom elements?

cc 👀: https://stackblitz.com/edit/vitejs-vite-4wwdax?file=package.json

yoyo837 · 2023-05-19T02:26:44Z

Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it too, you can use this plugin
https://github.com/baiwusanyu-c/unplugin-vue-ce/blob/master/packages/sub-style/README.md

Could I using regular Vue components with scoped styles tag inside custom elements?

cc 👀: https://stackblitz.com/edit/vitejs-vite-4wwdax?file=package.json

Duplicate css

baiwusanyu-c · 2023-05-19T02:29:02Z

Thanks, I'll check it out later, maybe there's something wrong with the plug-in injection code @yoyo837

baiwusanyu-c · 2023-05-19T02:46:50Z

Thanks, I'll check it out later, maybe there's something wrong with the plug-in injection code @yoyo837

Sorry, this is not a code problem. Before this test project, I manually pasted and copied 1000 style tags for testing.

lucasantunes-ciandt · 2023-06-01T17:47:03Z

@raffobaffo would your solution also inject styles into the shadow DOM from child components imported within the defineCustomElement component that originate from external packages?

As an example, if I define and export a component with defineCustomElement, but within that element is a button component that is being imported from an external package (and is not created with defineCustomElement).

Also @lucasantunes-ciandt do you have a working example using the reproduction repo?

Sorry, I haven't worked in this project in over a year now so I no longer have access to it. Hope you have fixed your issue or been able to use baiwusanyu-c's plugin!

lucasantunes-ciandt · 2023-06-01T17:52:32Z

Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it too, you can use this plugin
baiwusanyu-c/unplugin-vue-ce@master/packages/sub-style/README.md

Could I using regular Vue components with scoped styles tag inside custom elements?

cc 👀: stackblitz.com/edit/vitejs-vite-4wwdax?file=package.json

Duplicate css

I remember having this issue at the time, but the culprit was another one. In my case, I vaguely remember I was trying to @import .less (could be SCSS or other preprocessor in your case) mixins and variables in our main.ts file for them to be available in all components, but it would duplicate the CSS for every component we had, so instead I had to inject it by creating a global "theme" for our app. IIRC we used style-resources-loader for this, so Webpack would handle it during build time. Hope it helps 😅

SavkaTaras · 2023-08-11T19:42:25Z

Hey all,

I wanted to give a BIG THANK YOU to @baiwusanyu-c for creating unplugin-vue-ce and resolving #4662 issue on a plugin level.

Thank you for all your hard work @baiwusanyu-c !

https://github.com/baiwusanyu-c/unplugin-vue-ce/tree/master

Best regards,
Taras

padcom · 2023-12-14T10:44:48Z

We will solve this, it might take a few more days or weeks though.

@LinusBorg looks like it takes quite a bit more than a few days or weeks. Any idea when this will be fixed?

Grimille · 2024-01-17T18:07:27Z

Bump, we really need this...

seyfer · 2024-01-18T10:49:06Z

Bump, we really need this...

it will reduce the amount of hacks we have to implement, for sure. now everybody is solving this problem in different ways.

matthiasPOE · 2024-03-19T12:00:41Z

anyone managed to solve this cleanly yet?

dsmelon · 2024-05-16T03:49:41Z

Three years and still no resolution. This problem is not so simple to solve. The context of the webcomponent needs to be maintained, and the inserted style tags need to be marked to prevent repeated insertion when the component is used multiple times. Currently, I deprecated scoped, and all styles are imported into .ce.vue using @import. Expect an official fix soon

EranGrin · 2024-06-13T20:50:46Z

Just another plugin that resolves the issue as SFC or a full app
https://www.npmjs.com/package/vue-web-component-wrapper

dsmelon · 2024-07-31T03:22:58Z

Just another plugin that resolves the issue as SFC or a full app https://www.npmjs.com/package/vue-web-component-wrapper

有大bug，上面别人修复出现的问题基本全部出现了，一个组件多次使用，样式重复，element-plus的例子，组件样式上升到head标签里去了，而且大量重复的样式，仅仅解决了组件样式不生效的基本问题，不可靠

SavkaTaras · 2024-07-31T03:37:56Z

I used the following plugin to resolve all issues:
https://github.com/baiwusanyu-c/unplugin-vue-ce/tree/master

Works like magic. I understand this is not an official fix, but this is good.

mrcego · 2024-07-31T03:55:59Z

I used the following plugin to resolve all issues:
https://github.com/baiwusanyu-c/unplugin-vue-ce/tree/master

Works like magic. I understand this is not an official fix, but this is good.

Life saver, I'm using from its foundation. Kudos to @baiwusanyu-c for this masterpiece.

…t shadow root close #4662 close #7941 close #7942

…t shadow root (#11517) close #4662 close #7941 close #7942

yyx990803 · 2024-08-06T15:35:45Z

closed via #11517

LinusBorg added the scope: custom elements label Sep 23, 2021

raffobaffo added a commit to raffobaffo/vue-next that referenced this issue Sep 27, 2021

fix(customElementDependencyStyles): Recursively add styles from impor…

2de24dd

…ted components. Missing feature, store available styles to avoid dupes. close vuejs#4662

raffobaffo added a commit to raffobaffo/vue-next that referenced this issue Sep 28, 2021

fix(customElementDependencyStyles): Recursively add styles from impor…

dd13620

…ted components. Missing feature, store available styles to avoid dupes. close vuejs#4662

raffobaffo added a commit to raffobaffo/vue-next that referenced this issue Sep 28, 2021

fix(customElementDependencyStyles): Recursively add styles from impor…

2ee4ec7

…ted components. Missing feature, store available styles to avoid dupes. close vuejs#4662

raffobaffo mentioned this issue Sep 28, 2021

fix(custom-elements): Add children component styles fix #4662 #4695

Closed

Makoehle mentioned this issue Jan 18, 2022

Vue 3 Web Component target vuejs/vue-cli#6033

Open

tony19 mentioned this issue Mar 8, 2022

Vue web component nested styling vitejs/vite#5731

Closed

7 tasks

baiwusanyu-c mentioned this issue Nov 30, 2023

defineCustomElement causes style loss #9717

Closed

edison1105 mentioned this issue May 16, 2024

vue webcomponent 里使用vue组件，组件内部样式丢失 #10936

Closed

yyx990803 added a commit that referenced this issue Aug 5, 2024

feat(custom-element): inject child components styles to custom elemen…

fc32d55

…t shadow root close #4662 close #7941 close #7942

yyx990803 mentioned this issue Aug 5, 2024

feat(custom-element): inject child components styles to custom element shadow root #11517

Merged

yyx990803 added a commit that referenced this issue Aug 5, 2024

feat(custom-element): inject child components styles to custom elemen…

56c76a8

…t shadow root (#11517) close #4662 close #7941 close #7942

yyx990803 closed this as completed Aug 6, 2024

EranGrin mentioned this issue Aug 7, 2024

自定义组件样式重复，element-plus组件样式上升到页面head标签里 EranGrin/vue-web-component-wrapper#33

Closed

github-actions bot locked and limited conversation to collaborators Aug 21, 2024

When importing component inside custom element, style is discarded #4662

When importing component inside custom element, style is discarded #4662

Comments

gnuletik commented Sep 23, 2021

Version

Reproduction link

Steps to reproduce

What is expected?

What is actually happening?

tony19 commented Sep 27, 2021

raffobaffo commented Sep 27, 2021

gnuletik commented Sep 27, 2021

raffobaffo commented Sep 27, 2021

raffobaffo commented Sep 28, 2021 • edited Loading

pawel-marciniak commented Oct 14, 2021

LinusBorg commented Oct 14, 2021

pawel-marciniak commented Oct 14, 2021

raffobaffo commented Oct 16, 2021

lucasantunes-ciandt commented Nov 9, 2021

raffobaffo commented Nov 10, 2021

lucasantunes-ciandt commented Nov 11, 2021 • edited Loading

lucasantunes-ciandt commented Nov 11, 2021 • edited Loading

lucasantunes-ciandt commented Nov 11, 2021 • edited Loading

raffobaffo commented Nov 12, 2021

lucasantunes-ciandt commented Nov 13, 2021

adamdehaven commented Nov 24, 2021 • edited Loading

raffobaffo commented Nov 27, 2021 • edited Loading

adamdehaven commented Nov 27, 2021 • edited Loading

dezmound commented Nov 29, 2021 • edited Loading

Makoehle commented Jan 19, 2022

claudiomedina commented Feb 16, 2022

dezmound commented Feb 16, 2022 • edited Loading

Danny-Engelman commented May 17, 2023

soultice commented May 17, 2023

haoqunjiang commented May 17, 2023 • edited Loading

baiwusanyu-c commented May 18, 2023

mrcego commented May 18, 2023

baiwusanyu-c commented May 19, 2023

yoyo837 commented May 19, 2023

baiwusanyu-c commented May 19, 2023

baiwusanyu-c commented May 19, 2023

lucasantunes-ciandt commented Jun 1, 2023

lucasantunes-ciandt commented Jun 1, 2023 • edited Loading

SavkaTaras commented Aug 11, 2023

padcom commented Dec 14, 2023

Grimille commented Jan 17, 2024

seyfer commented Jan 18, 2024

matthiasPOE commented Mar 19, 2024

dsmelon commented May 16, 2024

EranGrin commented Jun 13, 2024

dsmelon commented Jul 31, 2024

SavkaTaras commented Jul 31, 2024

mrcego commented Jul 31, 2024

yyx990803 commented Aug 6, 2024

raffobaffo commented Sep 28, 2021 •

edited

Loading

lucasantunes-ciandt commented Nov 11, 2021 •

edited

Loading

lucasantunes-ciandt commented Nov 11, 2021 •

edited

Loading

lucasantunes-ciandt commented Nov 11, 2021 •

edited

Loading

adamdehaven commented Nov 24, 2021 •

edited

Loading

raffobaffo commented Nov 27, 2021 •

edited

Loading

adamdehaven commented Nov 27, 2021 •

edited

Loading

dezmound commented Nov 29, 2021 •

edited

Loading

dezmound commented Feb 16, 2022 •

edited

Loading

haoqunjiang commented May 17, 2023 •

edited

Loading

lucasantunes-ciandt commented Jun 1, 2023 •

edited

Loading