Open gmichael27 opened 2 years ago
We are also seeing the same issue, following the same git issue @gmichael27 listed above. Additionally, We have tried targeting specific angular versions with -v13/v12 with no success either.
Hello, if I remember correctly @GiladShoham fixed the ramda issue in react ui docs app a month ago, so this shouldn't appear anymore (as it's not longer used at all). Just to be sure, I've bumped the version of the dependency on react.ui.docs-app to the latest version and I've released new versions of all envs, can you update and check if it fixes the issue for you now?
That did it.
Ramda and angular were shown as changed when I ran bit update
and everything started without issue.
Thank you for your response
Thanks @ocombe, that did resolve the errors on startup and things boot up fine now.
I did want to mention one issue I'm seeing that seems like it may be related, since you mentioned react.ui.docs-app
. The code blocks out-of-the-box don't seem to have syntax highlighting when using the custom ENV. Here are screenshots of what I mean: when creating a new ng-workspace / ng-module and starting the server, code blocks look like this:
After creating the ng-env, updating workspace.jsonc as above / installing and starting again, code blocks now look like this:
Again, this is separate from the original problem but thought it may be related to the fix.
Interesting, I never noticed that, thanks
We're running into dependency issues when using a custom Angular env so that we can use Angular Material. Unfortunately, installation of it is not as simple as basic dependencies; the
ng add
schematic does some other behind-the-scenes work and must be run in an Angular app (which we are not using here). This lead us to find a couple existing issues with Angular Material and custom envs which we have used as a guide: https://github.com/teambit/bit-angular/issues/32 https://github.com/teambit/bit-angular/issues/35To start, we've set up a brand-new Angular workspace out-of-the-box: https://bit.cloud/teambit/angular/angular
Everything here seems to work fine. Next, we add a custom Angular env:
Following #35 above, we now edit our
workspace.jsonc
to link everything up properly:To be safe, we now delete
node_modules
,yarn.lock
, and runbit capsule delete --all
to clean up all existing dependencies. After, we run:Opening and viewing
angular-material-env
in the client results in the following errors in the console; something appears to be dependent onramda
/ramda-adjunct
, and fails out-of-the-box. We're wondering if there is a missing dependency somewhere, or if we have misconfigured our custom env.Some additional OS information: