Trying to figure out reason for EUNSUPPORTEDPROTOCOL / Unsupported URL Type "workspace:": workspace:packages/connectkit

[LuwkasLima]

Hello everyone, I'm curious to know if that could be a major issue...

I recently contributed with #82 to add translation to pt-BR and to not wait for the PR to be merged, decided to install it from my fork in the project I'm working currently. I'm using NPM on my project, so I decide to go ahead and run:

npm install LuwkasLima/connectkit#localizations/pt-BR

Once done, I npm uninstall connectkit and updated the code to import from the new package. However, I ended up having the following issue:

Unsupported url type "workspace:": workspace: package/connectkit

I've researched a bit to try to understand what could be causing the issue. Most of the people facing similar issues have decided to go for Yarn instead of NPM. I don't think that's a solution, but I gave it a try and indeed it allowed me to install the package, however I started having another issue:

error - ./node_modules/family-connectkit/packages/connectkit/src/components/Common/Avatar/index.tsx Module parse failed: Unexpected token (10:5) You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

| import useIsMounted from '../../../hooks/useIsMounted';
|
type Hash = '0x${string}';
|
| export type CustomAvatarProps = {

Import trace for requested module: ./node_modules/family-connectkit/packages/connectkit/src/components/Common/Avatar/index.tsx ./node_modules/family-connectkit/packages/connectkit/src/index.ts

I don't think setting up a custom loader on webpack will make sense here. I haven't changed anything from the original connectkit, so wondering if this could be something bigger than just conflict of dependencies due to a fork of the package.

any thoughts anyone?