-
Notifications
You must be signed in to change notification settings - Fork 16
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
Webpack build issues #4
Comments
Can you make sure your webpack is set up to compile TypeScript? Instructions are here: https://webpack.js.org/guides/typescript/ This shouldn't be happening in the CeramicIntegrationExample repo, though. I will investigate that now and follow up here. |
webpack: https://github.com/PrimeDAO/prime-deals-dapp/blob/3f9e8e8736d84664b738d7d0d885dc69b87386b1/webpack.config.js#L251 I looked into this issue webpack/webpack#10227, that proposed to change |
Hey, I just updated this package to 1.1.7. It provides the typescript precompiled, so it should "just work" and all the typescript errors should go away. Can you give it a try? I also updated https://github.com/LIT-Protocol/CeramicIntegrationExample to use it with Parcel and it works great. |
Has not fixed our issue unfortunately. Now it still points to another package
Still greatly appreciate the quick response and update! |
Bummer that it's still not working though! if you can't figure it out, and you're able to switch to Parcel instead of Webpack, that seems to work really smoothly. |
I'm trying to use this package, but encountered issues with webpack while building.
Also, I'm no bundling expert, so I'd like to get help in troubleshooting
Steps to reproduce
Note, both ways yield different errors, but underlying problem should be the same, and relates to
You should not need to recompile .ts files there, but if you really want to, use the allowTsInNodeModules option.See: microsoft/TypeScript#12358Edit: hmm, not sure anymore about this one
Quickest way it to use
Error log (expand)
Other
lit-ceramic-sdk
Error log (expand)
The text was updated successfully, but these errors were encountered: