There is a HTML tag for "Word Break Opportunity"
+ +For example: Kauf<wbr/>haus.
For example: Kauf<wbr/>haus.
git fetch $repo_url $remote_branch:$new_local_branch
For example:
+The following vite.config.ts:
+import { fileURLToPath, URL } from "url"
+import { defineConfig } from 'vite'
+import vue from '@vitejs/plugin-vue'
+
+// https://vitejs.dev/config/
+export default defineConfig({
+ plugins: [vue()],
+ resolve: {
+ alias: {
+ "~": fileURLToPath(new URL("./src", import.meta.url)),
+ "~component": fileURLToPath(new URL("./src/components", import.meta.url)),
+ "~composable": fileURLToPath(new URL("./src/composables", import.meta.url)),
+ "~lib": fileURLToPath(new URL("./src/lib", import.meta.url)),
+ }
+ }
+})
+will need this in tsconfig.json:
+{
+ "compilerOptions": {
+ "paths": {
+ "~/*": [ "./src/*" ],
+ "~component/*": [ "./src/components/*" ],
+ "~composable/*": [ "./src/composables/*" ],
+ "~lib/*": [ "./src/lib/*" ]
+ }
+ }
+}
+The asterixes in the syntax are important (alias/* => ./path/*).
On kernel updates I saw a recurring "EFI variables are not supported on this system", so I investigated and learned that the new EFI variables are provided via a file system that needs to be mounted first:
+mount -t efivarfs efivarfs /sys/firmware/efi/efivars
+For example:
+% pwdx 1984
+> 1984: /home/george/ttlctrl
+If you want to mock an imported function in Jest in a way that allows you to check if it has been called, you can not do the seemingly straighforward:
+// mock prefix necessary btw
+const mockThatFunction = jest.fn(() => 'stuff')
+
+jest.mock('@/path/to/module', () => ({
+ thatFunction: mockThatFunction,
+}))
+
+// ...in test descriptions
+expect(mockThatFunction).toHaveBeenCalled()
+This way thatFunction will be undefined without anyone telling you why.
+What you need to do instead:
+import { thatFunction } from '@/path/to/module'
+
+jest.mock('@/path/to/module', () => ({
+ thatFunction: jest.fn(() => 'stuff'),
+}))
+
+// ...in test descriptions
+expect(thatFunction).toHaveBeenCalled()
+Today I was about to push a focussed test. A focussed test, you ask?
+In Jest (and others) one can run only a specific test, by writing it.only(.... Pushing this to production might create some funny or not so funny side effects though. Luckily there is the no-focussed-tests linter rule in eslint-plugin-jest.
users.sort((a, b) => a.firstname.localeCompare(b.firstname))
+or reversed order:
+users.sort((a, b) => a.firstname.localeCompare(b.firstname) * -1)
+