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

Resolve TypeError: cli.isMultipleCompiler is not a function errors on local startup #789

Open
rgraber opened this issue Nov 3, 2022 · 4 comments

Comments

@rgraber
Copy link
Contributor

rgraber commented Nov 3, 2022

Publisher fails to start up when run in devstack with make dev.up.frontend-app-publisher. The error is TypeError: cli.isMultipleCompiler is not a function. This can be fixed locally by manually installing webpack-cli@4.10.0 and/or bootstrap@4.6.1 in the shell but the app should work on startup without needing extra commands.

It's possible the solution is to upgrade to the latest version of Paragon (to bring in this fix: openedx/paragon#1562) but this causes dependency conflicts:

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @edx/frontend-component-footer-edx@4.4.1
npm ERR! Found: @edx/frontend-platform@3.0.1
npm ERR! node_modules/@edx/frontend-platform
npm ERR!   @edx/frontend-platform@"3.0.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer @edx/frontend-platform@"^2.4.0" from @edx/frontend-component-footer-edx@4.4.1
npm ERR! node_modules/@edx/frontend-component-footer-edx
npm ERR!   @edx/frontend-component-footer-edx@"4.4.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: @edx/frontend-platform@2.6.2
npm ERR! node_modules/@edx/frontend-platform
npm ERR!   peer @edx/frontend-platform@"^2.4.0" from @edx/frontend-component-footer-edx@4.4.1
npm ERR!   node_modules/@edx/frontend-component-footer-edx
npm ERR!     @edx/frontend-component-footer-edx@"4.4.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /root/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-11-03T14_24_04_291Z-debug-0.log
@Mashal-m
Copy link
Contributor

Mashal-m commented Nov 7, 2022

Hey, can you please share your node version?
It's working fine for us, our node version is v16.15.0

@ishahroz
Copy link
Member

Hi @rgraber , I have tried upgrading paragon version to the mentioned 20.9.2 version and was able to successfully build and run frontend-app-publisher through devstack with make dev.up.frontend-app-publisher. Moreover, I am also able to build and run this repo on the current version of paragon, i.e., 19.14.0 because as earlier mentioned, the issue was probably be working when installing bootstrap@4.6.1 via shell and this dependency is already on the same version in paragon@19.14.0.

Can you please share the sequence of steps of how you are facing this issue exactly?

@rgraber
Copy link
Contributor Author

rgraber commented Feb 2, 2023

Sorry for the delay. After running make dev.down.frontend-app-publisher, make dev.pull.frontend-app-publisher, and updating my repo I'm able to actually start the service. Now, however, when I try to open it in the browser, I get an error in the console (screenshot provided)
Screenshot 2023-02-02 at 10 56 50 AM

@abdullahwaheed
Copy link
Contributor

rebuilding docker images doesn't raise error either 😢
could you please check network tab of chrome as well. I think some inconsistent backend data might be causing this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants