Mage H.D. Inc
Mage H.D. Inc
> Hey @teknology , all the recent issues (#33 , #32 ) you opened indicates an inaccurate packages resolution, there's no yarn.lock in this repo, please use npm to fix...
> Hey @teknology , all the recent issues (#33 , #32 ) you opened indicates an inaccurate packages resolution, there's no yarn.lock in this repo, please use npm to fix...
A quick update. I fixed Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './lib/parser' is not defined by "exports" in /Users/Tek/Documents/Sites/aareact/node_modules/next/node_modules/postcss/package.json By running `nvm use 16 rm -rf node_modules npm install npm run dev...
That's not really a fix.
@RemCom Are they even responding?
I wish i knew that before pressing the lock button. I thought it was some sort of security that needed an admin code. How is the current way it works...
> [@teknology](https://github.com/teknology) untick strip prefix in console and realtime settings That didn't solve the issue. It resulted in Realtime link reporting a 400 bad request and console still has a...
> +1 I'm facing the exact same issue as described by [@teknology](https://github.com/teknology) I switched the proxy to Traefek. I was told Caddy has a bug waiting to merge.