You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the error in the title when I try to use this library in a typescript project with the following settings in tsconfig.json
{
"strict": true,
"skipLibCheck": false
}
Here is a minimal project that reproduces the issue when you run npm install
It seems to be caused by a mismatch in layout between the source tree and the dist file tree.
In dist/to-string.d.ts, the .util/bases path is no longer valid, it should be ../util.bases
Perhaps this is an aegir bug ( ipfs/aegir#759ipfs/aegir#849 ), but I think it can also be worked around if the source files are moved to a src/ folder instead of the root dir. That should keep the path consistent in both source and dist situations.
Edit:
It seems the files are placed correctly by aegir but are excluded from packing by the very strict files entry in package.json.
Edit:
This bug has been introduced in 99c8aaa so it affects versions 2.1.6 & 2.1.7
The text was updated successfully, but these errors were encountered:
mirceanis
added a commit
to mirceanis/uint8arrays
that referenced
this issue
Jul 27, 2021
I get the error in the title when I try to use this library in a typescript project with the following settings in tsconfig.json
Here is a minimal project that reproduces the issue when you run
npm install
It seems to be caused by a mismatch in layout between the source tree and the
dist
file tree.In
dist/to-string.d.ts
, the.util/bases
path is no longer valid, it should be../util.bases
Perhaps this is an aegir bug ( ipfs/aegir#759 ipfs/aegir#849 ), but I think it can also be worked around if the source files are moved to asrc/
folder instead of the root dir. That should keep the path consistent in both source and dist situations.Edit:
It seems the files are placed correctly by
aegir
but are excluded from packing by the very strictfiles
entry inpackage.json
.Edit:
This bug has been introduced in 99c8aaa so it affects versions 2.1.6 & 2.1.7
The text was updated successfully, but these errors were encountered: