steven

For this to work, the `@Module({ name: 'some/path' })` option has to be updated to support an array `name: ['some', 'path']`. Internally, after this framework hands the module off to...

I was going to go the suggested route of using computed properties to expose module values and testing those. But then I also didnt want to refactor computed properties to...

So the way I ended up making these work with my original app layout was though hoisted jest mocks. It depends on jest to execute the mock first before any...

so i have this problem still. im using `"workbox-webpack-plugin": "^5.1.4"` basically we have a vendor build and an app build: ```bash # from vendor Asset Size Chunks Chunk Names 205f07b3883c484f27f40d21a92950d4.ttf...

So another update. Looking back at our git history has revealed back when we used version 4 we depended on the following `InjectManifest` plugin options: https://developers.google.com/web/tools/workbox/reference-docs/latest/module-workbox-build#.injectManifest Parameter | Type |...

After having a coworker point out that the document link above clearly references `6.1.5` 🤦 I upgraded and repeated the build and still see the same error output. ```jsonc //...

Awesome thanks for that clarification! So then `additionalManifestEntries` is the correct way forward with capturing that information? If `additionalManifestEntries` is the way to go my hash generation technique employed above...

I have a similar problem with vscode-jest and vue-jest. The configuration seems right because the tests are being found and run however they all fail on `import Vue from 'vue'`....

i preformed the following: uninstalled jest, installed jest in WSL. toggling coverage and the setup extension beta option result in errors such as this:  since this project has no...

What i did was write routes.js, then import it using require into vue.config.js and process it using helper modules to add my dynamic configuration. ```js //routes.js const viewOption = {...