As suggested in the comments, the answer here are circular dependencies. There is actually no circular dependency present in the code provided in the question (because it’s just a simplified snippet of code) but the symptoms are very clear. The simplest example of a circular dependency is when file A imports file B and file … Read more
Thanks to this reply: https://stackoverflow.com/a/54117206/15741905 I started googling for similar fixes and ended up here: https://github.com/uuidjs/uuid/issues/451 And this solved my problem: https://github.com/uuidjs/uuid/issues/451#issuecomment-1112328417 // jest.config.js { //……………. moduleNameMapper: { // Force module uuid to resolve with the CJS entry point, because Jest does not support package.json.exports. See https://github.com/uuidjs/uuid/issues/451 “uuid”: require.resolve(‘uuid’), } } Tough I would still … Read more
Using Watch Expressions on the right hand side, usually solves this. Expand the menu, and use the plus button to add your variables. You can use someNumber and someOtherNumber, and even someNumber + someOtherNumber.
While the answers here are all correct, Babel is not just about ES6 (ES2015). The ECMA standards committee has agreed to release yearly updates to the JavaScript language. Babel will always integrate the standards, whereas we don’t know if all the browsers will, and if they do, whether they will be able to keep up … Read more
VS Code 1.41 supports optional chaining in both JavaScript and TypeScript files. This support includes syntax highlighting and IntelliSense. If you are using VS Code 1.41+ and optional chaining is not working as expected, try: Check your installed extensions. Some of them may not yet understand optional chaining, which could cause errors or bad syntax … Read more
Using Babel 6.x, let’s say we have file test/pad.spec.js: import pad from ‘../src/assets/js/helpers/pad’; import assert from ‘assert’; describe(‘pad’, () => { it(‘should pad a string’, () => { assert.equal(pad(‘foo’, 4), ‘0foo’); }); }); Install a bunch of crap: $ npm install babel-istanbul babel-cli babel-preset-es2015 mocha Create a .babelrc: { “presets”: [“es2015”] } Run the tests: … Read more
My solution is to not use this at all, but use the variables that are passed to the callback function. The first one is the index and the second one gives you the DOM element itself. let mediaBoxes = $(‘.now-thumbnail’); let titles = []; mediaBoxes.each((index, element) => { let obj = { index: index, title: … Read more
We are using import.meta.url to make use of web workers, for example using the native worker support in Webpack 5. That works great but fails when running the Jest tests. babel-vite-preset does not handle this as far as I can tell. The top answer about extracting and mocking the code that uses import.meta does work … Read more
When you are destructuring an Object, you need to use the same variable names as the keys in the object. Only then you will get one to one correspondence and the values will be destructured properly. and you need to wrap the entire assignment in parenthesis if you are not using declaration statement, otherwise the … Read more
I eventually found out what the problem was. It turns out it was there in ts-jest’s README all the time. There’s a section in the README titled Using ES2015+ features in Javascript files. In these cases, you need to instruct jest to use babel-jest as a transform for .js files. “jest”: { “transform”: { “^.+\\.jsx?$”: … Read more