Skip to content
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

Fixed issue with exports #22

Closed
wants to merge 1 commit into from
Closed

Fixed issue with exports #22

wants to merge 1 commit into from

Conversation

bashleigh
Copy link
Contributor

#21 Imports needed relative path and build required lib dom

@bashleigh bashleigh added the bug label Jan 29, 2019
@bashleigh bashleigh self-assigned this Jan 29, 2019
@@ -15,7 +15,7 @@
"rootDir": "./src",
"baseUrl": "./",
"outDir": "./dist",
"lib": ["es2017"]
"lib": ["es2017", "dom"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we need dom ?! 😮

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I thought you would say this! Apparently there's an issue with superagent DefinitelyTyped/DefinitelyTyped#12044 that requires the dom library. I didn't like it but it was the quickest fix but yea. I probably shouldn't have added it. Another method is to create a file declaring the Blob and XmlHttpRequest interfaces and I didn't like that neither

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, That sounds weird but ok.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think the dom library is a good idea tbh

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

me too, but anyway we need to investigate more to see what cusses this issue.
is that a typescript issue ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking it might be because I had a different version of node running when I previously built the package?

@jkernech
Copy link

jkernech commented May 7, 2019

Any news on this PR?

@logicflakes
Copy link

Still not working, any update?

@jkernech
Copy link

Hey @bashleigh, can I do something to help out on this one?

@bashleigh
Copy link
Contributor Author

@jkernech yes please! I'm struggling with my work load and this one is at the back of the queue. There's an issue with building the package for release. Need to remove lib that I added and figure out why the exception is thrown from tsc. Thanks! I'll do my best to come back to this!!

@bashleigh bashleigh closed this Aug 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants