Merge pull request #2463 from opral/parjs-45--not-being-cleared

Document page-data sideeffect quirk

.changeset/mighty-brooms-leave.md

@@ -0,0 +1,6 @@
+---
+"@inlang/paraglide-js-adapter-unplugin": patch
+"@inlang/paraglide-js": patch
+---
+
+fix `openRepository` crash in non-git environments

inlang/source-code/paraglide/paraglide-js-adapter-sveltekit/README.md

@@ -313,6 +313,7 @@ export async function load({ depends }) {
 
 1. Links in the same Layout Component as `<ParagldieJS>` will not be translated. This will also log a warngin in development.
 2. Messages are not reactive. Don't use them in server-side module scope.
+3. Sideeffects triggered by `data` will run on language changes even if the data didn't change. If the data is language-dependent the sideeffect will run twice. 
 
 ### Using messages in `+layout.svelte`
 

inlang/source-code/paraglide/paraglide-js-adapter-unplugin/src/index.ts

@@ -64,7 +64,7 @@ export const paraglide = createUnplugin((config: UserConfig) => {
 
 		const repoRoot = await findRepoRoot({ nodeishFs: fs, path: projectPath })
 
-		const repo = await openRepository(repoRoot || process.cwd(), {
+		const repo = await openRepository(repoRoot || "file://" + process.cwd(), {
 			nodeishFs: fs,
 		})
 

inlang/source-code/paraglide/paraglide-js/src/cli/commands/init.ts

@@ -44,7 +44,7 @@ export const initCommand = new Command()
 		// We are risking that there is no git repo. As long as we only use FS features and no Git features
 		// from the SDK we should be fine.
 		// Basic operations like `loadProject` should always work without a repo since it's used in CI.
-		const repo = await openRepository(repoRoot ?? process.cwd(), {
+		const repo = await openRepository(repoRoot ?? "file://" + process.cwd(), {
 			nodeishFs: nodeFsPromises,
 		})