fix: absolute paths error on windows about nuxt-cookie-control

[ennioVisco]

Also, thx @mshadowz for providing a workaround!

I suggest you re-enable Windows here:

nuxt-cookie-control/.github/workflows/ci.yml

Line 13 in 5a1742b

os: [ubuntu-latest] # macos-latest, windows-latest temporarily disabled (https://github.com/nuxt/framework/issues/8461)

since nuxt/nuxt#15249 has been resolved!

[dargmuesli]

Thank you for reporting that issue. I currently do not have a Windows installation at hand, so whoever feels like submitting a PR is welcome to do so!

[dargmuesli]

cc nuxt-modules/robots#86

[dargmuesli]

@AndreasKubasa would you mind to check if #22 fixes the issue for you?

[AndreasKubasa]

@AndreasKubasa would you mind to check if #22 fixes the issue for you?

to be honest, I tested, but now it throws couple more other errors, so clearly changes something, I guess we need to trust :)

[dargmuesli]

Throwing a couple more errors is not necessarily a qualification for a merge, I reckon 😅😂 I'd merge it once I get feedback by the PR creator to open questions.

[oscarvadillog]

PR #22 doesn't work for me either. Has anyone been able to fix it?

[dargmuesli]

Upstream issue

• nuxt/nuxt#15500

[mshadowz]

yes. if we apply these changes in module.mjs f

addImports({
name: "useCookieControl",
as: "useCookieControl",
from: resolve(runtimeDir, "composables")
});

to this :

addImports({
name: "useCookieControl",
as: "useCookieControl",
from: resolver.resolve(runtimeDir, "composables")
});

and also change this :

const text = await import(await resolvePath(resolve(runtimeDir, "locale", locale))).then((r) => r.default || r);

to this :

const path = await resolvePath(resolver.resolve(runtimeDir, "locale", locale));
const finalPath = (process.platform == "win32") ? "file:///" + path : path;
const text = await import(finalPath).then((r) => r.default || r);

[dargmuesli]

Would you guys please try nuxt v3.2.3 with @dargmuesli/nuxt-cookie-module v5.0.1 and report if fixes in those releases resolve this issue?

[dargmuesli]

Also, thx @mshadowz for providing a workaround!

[dargmuesli]

Please try v5.0.2 once released and report if the issue is resolved :)

[dargmuesli]

🎉 This issue has been resolved in version 5.0.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀