After some testing, the simple solution was to be sure to export a Vue.extend() object rather than a plain object for any component being extended. In my case, the base component: import Vue from ‘vue’ export default Vue.extend({ [component “Foo” definition] }) and the extended component: import Foo from ‘./Foo’ export default Foo.extend({ [extended component … Read more
For anyone else that was combing through the internet like I’ve been – looking for a solution to this when testing with Jest – I will back up the answer by @biphobe by saying Jest will cause this error to occur when you export something inside the same file that is calling ReactDOM.render. In my … Read more
There are several ways to have global values available in your application. Using ES6 modules, you can create a constant which you export from your module. You can then import this from any other module or component, like so: /* Constants.js */ export default { VALUE_1: 123, VALUE_2: “abc” }; /* OtherModule.js */ import Constants … Read more
In webpack config there are multiple things for configuration, the most important ones are entry – can be an array or an object defining the entry point for the asset you want to bundle, can be a js as test here says do it only for /.js$. Your application if has multiple entry points use … Read more
After doing some more research, I’ve found: Imports ARE hoisted! according to the spec of ModuleDeclarationInstantiation ALL the dependent Modules will be loaded before running any code. This code will have no errors, and will work: localFunc(); import {myFunc1} from ‘mymodule’; function localFunc() { // localFunc is hoisted myFunc1(); }
You can use toJSON method to customise the way your class serialises to JSON: class MyClass { constructor(property) { this.property = property } set property(prop) { // Some validation etc. this._property = prop } get property() { return this._property } toJSON() { return { property: this.property } } }
This is caused by an extension passing these extra attributes with your code when it is executed on the browser trying to interact with the UI . Extensions similar to Grammarly and LanguageTool are therefore the cause of this warning, so you have to find out which one is doing this then disable/configure it. You … Read more
The best solutions I’ve found have been libraries like https://github.com/stalniy/bdd-lazy-var and https://github.com/tatyshev/given2 If you don’t want to introduce a dependency, you can get similar behavior (albeit without lazy evaluation) by doing something like this: beforeEach(() => { let input=”foo”; beforeEach(() => { setupSomeThing(input); }); describe(‘when input is bar’, () => { beforeAll(() => { input=”bar”; … Read more
for..in When looking at the Typescript documentation (Typescript: Iterators and Generators), we see that the for..in syntax will iterate over the keys of the object. for..in returns a list of keys on the object being iterated, whereas for..of returns a list of values of the numeric properties of the object being iterated. We can use … Read more
No, ES6 classes are not just syntactic sugar for the prototypal pattern. While the contrary can be read in many places and while it seems to be true on the surface, things get more complex when you start digging into the details. I wasn’t quite satisfied with the existing answers. After doing some more research, … Read more