devtools VS Bit

I've tried everything listed here for v3/standalone devtools and had no luck. Either CSP issues related to V3 or the inspector complains about the source maps not being found, but clicking the link brings you to the file location.

Vue Devtools

It seems as though it may be this issue: https://github.com/vuejs/devtools/issues/1974

The VueJS DevTools has a different team with a different leader. That's collaboration.

I think you are missing an important part here, this extension is open source, meaning everyone can check what they do with the info, meaning if something fishing is happening would be a big mess. for me, there is nothing to be worry about. you can also read the code and check. https://github.com/vuejs/devtools

All I can suggest is Vue Devtools

I don't know for sure, but I think the vue-devtools browser plugin ( https://github.com/vuejs/devtools ) works with the dev server to help track and debug state (mutations, actions, etc) as well as template issues, etc. I'm not sure how it works. I assume it's 10% code and 90% magic of some shade.

Source: Devtools

Our demo solution was built using Bit, which allows us to create shareable components, render component “previews,” generate component docs, and so on.

UI libraries come with their own set of challenges, which greatly limit their effectiveness. These challenges stem from more fundamental problems related to code sharing and reuse. Let’s explore some of these challenges and examine how a new entity, the Bit component, addresses them.

The following diagram showcases how bit shows the dependency graph of modified components and their dependents.

This tutorial demonstrates how to build a micro frontend application using Vite and Bit.

Bit: A next-generation build system for composable software.

Bit drives a paradigm shift in the way we structure our software and collaborate on code. Its component-based approach produces more maintainable projects and more effective collaboration. However, the power of Bit is best harnessed when you adopt a certain mindset. This blog aims to guide you through the core principles and methodologies of building software with independent Bit components.

And one such tool that I've found that supports this component-driven approach is Bit.

This blog will explain how Bit can be used to implement any architecture and transform “fatal” decisions that seem too hard to change into decisions that are easy to make and change.

Oh can I address theses issues. I already looked at tools like Nx or Bit, but they aren't matching our needs with closed source libs.

To begin, you need to prepare your environment. A few ways to build a React package include tools like Bit, Storybook, Lerna, and TSDX. However, for this tutorial, you will use a zero-configuration bundler for tiny modules called Microbundle.