TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "reacts to paramsupdated". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "uses test url in dev". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "doesnt remove visible when cookie is set". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "doesnt mount when feature is not toggled". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "initializes boost on click and shows panel after init". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "initializes boost with correct config". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "inits boost with dev url base". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "sets preferred filter to arbeidsgiver". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.

TypeError: Cannot read properties of undefined (reading 'open_chat') ❯ Object.render src/i18n.ts:5:45 ❯ new Chatbot src/views/chatbot.ts:41:31 ❯ Function.invokeTheCallbackFunction.construct ../../node_modules/jsdom/lib/jsdom/living/generated/CustomElementConstructor.js:23:30 ❯ upgradeElement ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:110:34 ❯ invokeCEReactions ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:186:13 ❯ ceReactionsPostSteps ../../node_modules/jsdom/lib/jsdom/living/helpers/custom-elements.js:54:3 ❯ HTMLDivElement.set innerHTML [as innerHTML] ../../node_modules/jsdom/lib/jsdom/living/generated/Element.js:1540:9 ❯ stringFixtureSync ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:18:24 ❯ stringFixture ../../node_modules/@open-wc/testing-helpers/src/stringFixture.js:37:14 ❯ Module.fixture ../../node_modules/@open-wc/testing-helpers/src/fixture-no-side-effect.js:59:12 This error originated in "src/views/chatbot.test.ts" test file. It doesn't mean the error was thrown inside the file itself, but while it was running. The latest test that might've caused the error is "sets preferred filter to nynorsk". It might mean one of the following: - The error was thrown, while Vitest was running this test. - If the error occurred after the test had been completed, this was the last documented test before it was thrown.