benjgil

Hi @rickykenny Your example env had a few issues, which once clearing up then fix the main issue in this thread, but throw up another bug that i'll open. Issues...

@rickykenny Apologies also for the delayed response to your questions above. Aspects and envs are two concepts which are central to bit, but shouldn't be confused. Aspects, and specifically with...

FYI @p-l-l and anyone else interested here We will be moving soon to targeting ESM by default from bit's component compilation (can be adjusted by overriding an env's tsconfig), which...

Hi there The command should have been `bit create react react-env --aspect teambit.react/react-env`, with the `--aspect` flag, not `--env` - with the --env flag it's very likely the env template...

Hi @coreyaus Yep that should definitely be updated in the docs (we've been moving a lot of scopes around recently, still catching up with the docs), though the command should...

Great question - it's probably based on a slight confusion about what a bit-app is, so i'll try to quickly clear up. A bit-app component is just another standalone component,...

It looks like there's a general issue with installing bit via npx when legacy is installed Please install `bvm` locally via `npm i -g @teambit/bvm` and then continue with your...

Hi there Yes this is possible, and indeed bit workspaces are built to be able to isolate all components' (including app components) dependencies. But you would need to let bit...

As with the core react package, as long as you use the correct env (react-17 for the react17 app, react18 for react18 app), the app's env will configure the correct...

Dependency management is a massive complication for when creating isolated code packages (components), and we've done a lot of work on perfecting it with bit (still not perfect, but light-years...