-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
Typescript dep expected with ReactJS #447
Comments
Same issue with
|
I have the same issue. My project is not using Typescript but I am forced to add |
This is weird because typescript is in no way a dependency of CRACO (it's a dev dependency for development but the published version does not require TS). @fryorcraken I cloned your repo and tested your |
This is what I get as soon as I remove typescript from node_modules:
|
@fkrauthan I'd probably recommend against deleting the whole typescript directory from node_modules because even though craco doesn't require it directly, there are other packages that do. You can try doing a fresh install by deleting your node_modules folder and then running |
@dilanx sorry but deleting I mean removing it from my package.json as devDependency. Which in return seem to show that at least in my project nothing requires Typescript except somehow Craco (as shown in the error message tree). |
@fkrauthan are you using npm as your package manager? |
I am using |
@fkrauthan hmm interesting. I've been testing out different things for a couple of hours. It looks like this is only an issue when using yarn. Even when I tried adding It looks like yarn doesn't resolve the peer dependencies of |
Hmm interesting. Any idea why this only started happening with the new 7.x version and not with the current live version? And is there anyway to dynamic load |
I might be hitting a similar issue. When I run
I'm using v7.0.0-alpha.8. EDIT Oh, just seeing this now: #435 After adding |
Continuing from above, this looks to be fixed in the latest version of https://github.com/Codex-/cosmiconfig-typescript-loader/blob/main/package.json#L36-L41 Is there a reason why we're pegged at v1.0.0 and aren't using the latest release? |
@curtvict craco 6 is no longer supported, but craco 7 alpha does use the latest release. It appears that this is still an issue even then. |
Ah, I was on the wrong branch. Thanks for pointing that out! I'll see if I can get this fixed upstream. Thanks again for your hard work on this. |
@curtvict @fkrauthan @fryorcraken I've found a solution that seems to work for now. It seems like it was definitely an issue with the latest version of |
Thanks for that, I can confirm the issue is gone with alpha.9 as demonstrated in waku-org/examples.waku.org#144 |
Yep, for me too; I was able to remove |
Using
@craco/craco@7.0.0-alpha.7
with a ReactJS application.Application can be found here: https://github.com/waku-org/js-waku-examples/tree/upgrade-js-waku/relay-reactjs-chat
craco.config.js
:When running
craco build
I am getting:Is that expected? If so,
typescript
should be added as a peer dependency of@craco/craco
, right?The text was updated successfully, but these errors were encountered: