New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TS Errors when importing ReactLinearGenomeView #3765
Comments
that is really odd that adding @types/jest fixes all the errors. I think I can confirm locally too. we can likely do the inlinesourcemaps change and see if that helps though |
Yeah the jest import thing confounds me... |
added a change in #3771 and tested out your repro with the change, should hopefully be fixed next release! |
@joneubank published v2.6.2 with no source maps/src folder (inline source maps still needed src folder to do properly, but we dont mangle our builds too much so just published with no source map) also fixed an error with the @jbrowse/react-circular-genome-view. lemme know if there are any other issues you run into! |
(the react-circular-genome-view issue that was fixed was properly publishing commonjs code in the dist folder) |
Describe the bug
Projects importing JBrowse React Linear View have errors running
tsc
. There are*.ts
in the/src
directory of the imported dependency, insidenode_modules/
, and these are failing TS type checking.To Reproduce
A repository with a minimal project showing how to reproduce is here: https://github.com/joneubank/minimal-reproduce-jbrowse-component-build
Steps to reproduce and a further description of the errors are in the README of that repo.
Expected behavior
Should be able to run
tsc
build on a project importing JBrowse React Linear Genome View, without having to modify ourtsconfig
or needing additional 3rd party dependencies.Screenshots
Version:
Additional context
This issue did not occur for us with the Circular Genome View, even though that repo also exports the
/src
folder. I would recommend removing the/src
files from the exported pacakges to prevent this kind of error in the future.This relates to #3764 and the two may in fact be duplicates now.
The text was updated successfully, but these errors were encountered: