Open arthurlomakin11 opened 2 years ago
Hey! Why don't you do anything?
sorry, @arthurlomakin11 for not responding. I am in vacation now, without my notebook.
can i ask you to prepare a PR? can you try to use import txml from 'txml/dist/txml'
or import txml from 'txml/txml'
? then it should not depend on the File
. @manzt do you know a solution?
@arthurlomakin11 how do you build your project? what is node version? typescript version? other build tools? babel?
sorry, @arthurlomakin11 for not responding. I am in vacation now, without my notebook.
can i ask you to prepare a PR? can you try to use
import txml from 'txml/dist/txml'
orimport txml from 'txml/txml'
? then it should not depend on theFile
. @manzt do you know a solution?@arthurlomakin11 how do you build your project? what is node version? typescript version? other build tools? babel?
Node - 16.5.0 Typescript - 4.5.3 Just using tsc.
@TobiasNickel import txml from 'txml/dist/txml'
and import txml from 'txml/txml'
don't work. It says there is no txml exported
@arthurlomakin11 using import * as txml from 'txml/dist/txml';
fixes the console errors
@arthurlomakin11 using
import * as txml from 'txml/dist/txml';
fixes the console errors
It just says that there's no txml in txml/dist/txml on runtime.
Any updates?
I am investigating if I should switch the build process to parcel.js in the hope, that it roduces more reliable a build that works for node, typescript, commonJS, the new es modules and work in browser (without node streams).
Having a similar issue
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './dist/txml' is not defined by "exports" in /.../node_modules/txml/package.json
When uploading to GCP
I am investigating if I should switch the build process to parcel.js in the hope, that it roduces more reliable a build that works for node, typescript, commonJS, the new es modules and work in browser (without node streams).
That's definitely good idea!
Are there any news?
import * as txml from 'txml/dist/txml';
doesn't fix it on my side, as it's not available at runtime
Hey @TobiasNickel - our organization is trying to use this library as well and running into same issues, unfortunately we can't introduce this because the console errors would interrupt our dev environment. Is there any chance you can merge the Pull Request for this fix and put out a new version??
Have a lot of errors and it's annoying.