Search

UPDATE: running pnpm run translations:generate (and also the other translations tasks, just to be sure) fixed the issue.

---

When trying to setup a local Lemmy instance (for development), the lemmy-ui repository throws an error when trying to start the dev server.

I followed the guide: https://join-lemmy.org/docs/contributors/02-local-development.html

When running pnpm dev to start the dev server, it presents me with two errors:

```bash

ERROR in ./src/shared/services/I18NextService.ts 14:0-40 Module not found: Error: Can't resolve '../translations/en' in '/home/ff0000/workspace/lemmy/lemmy-ui/src/shared/services' resolve '../translations/en' in '/home/ff0000/workspace/lemmy/lemmy-ui/src/shared/services' using description file: /home/ff0000/workspace/lemmy/lemmy-ui/package.json (relative path: ./src/shared/services) using description file: /home/ff0000/workspace/lemmy/lemmy-ui/package.json (relative path: ./src/shared/translations/en) no extension /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en doesn't exist .js /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en.js doesn't exist .jsx /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en.jsx doesn't exist .ts /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en.ts doesn't exist .tsx /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en.tsx doesn't exist as directory /home/ff0000/workspace/lemmy/lemmy-ui/src/shared/translations/en doesn't exist @ ./src/shared/dynamic-imports.ts 6:0-69 48:17-41 @ ./src/server/index.tsx 16:0-65 47:2-22

ERROR in ./src/shared/services/I18NextService.ts 159:43-129 Module not found: Error: Can't resolve '../translations' in '/home/ff0000/workspace/lemmy/lemmy-ui/src/shared/services' @ ./src/shared/dynamic-imports.ts 6:0-69 48:17-41 @ ./src/server/index.tsx 16:0-65 47:2-22

webpack 5.91.0 compiled with 2 errors in 14393 ms ``` I do see that these files nor the folder exist where I18NextService is trying to locate them. But i also see in the root a lemmy-translations folder.

I am able to get it sort of working by updating the paths in I18NextService, but i guess that is not the preferred approach.

see also: https://lemmy.world/post/1218097

The UI should at least display an error message.

On lemmy.world (where I'm mostly at) I see local communities getting posts in threads that are clearly for another thread. World still runs on 0.17.3, as the captcha is disabled in 0.18.0 and 0.18.1-rc1 gave issues.

Is this a known issue with federation between versions or limited to the old version?

First off, I apologize if I'm asking something that has been talked about over and over, but I didn't find much relevant information so far (aside from what I will discuss below).

From what I understand, post tags/flairs are a requested feature, but from @[email protected]'s comment here, tags are already a thing?

Or does his answer mean that people can use a special syntax (like [foo] or ::bar::) in post titles, which can then be searched like any other token?

Either way, I think it makes sense to allow tags in posts, like mastodon allows #hashtags, if only for the purpose of classification and moderation.

Indeed, I was looking at an eventual way to link https://lemmy.ml/c/Jerboa to the Jerboa issues on GitHub using GitHub actions and this action, and the main problem I can see with this is the lack of machine-readable marker to differentiate bug reports and issues from the rest of the conversation on the community.

Do Lemmy mods have the permissions to edit a post's title? In which case they could indeed prefix bug reports and issues with [bug] or [issue].