custom-elements-everywhere
feelback-integrations
custom-elements-everywhere | feelback-integrations | |
---|---|---|
19 | 12 | |
1,135 | 27 | |
0.5% | - | |
8.9 | 8.2 | |
6 days ago | 3 months ago | |
JavaScript | TypeScript | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
custom-elements-everywhere
-
Unlocking the frontend – a call for standardizing component APIs pt.2
With React (it seems) finally moving to support everything needed (they are the last major framework lagging behind substantially), too, we might be moving to a world post-framework discussions, and real interoperability on a technical level. I think Jake Lazaroff motivates this beautifully with his articles “Web Components Eliminate JavaScript Framework Lock-in” and “The Web Component Success Story”.
-
Use web components for what they’re good at
Seems it doesn’t work in React, everything is sent as a string. There was a link in the article that shows how well web components work with various frameworks.
https://custom-elements-everywhere.com/
You can see how React fares for itself.
-
If Web Components are so great, why am I not using them?
React supports Web Components, just some quirks to be aware of: https://custom-elements-everywhere.com/
-
[AskJS] Asking advice on monorepo setup with multiple frameworks
You could wrap each component as a Web Component and then import them for each repo. Web Components are not native to frameworks, so the support for them could vary when passing props. Or you could wrap the render method of each framework as a function and then use the receiving frameworks life cycle method and inject it onto the page. If you use frameworks like Svelte or Lit that are "Web Component" based, then you'd need to see if the receiving framework supports Web Components inorder to import the seamlessly.
-
Am I the only one that thinks that the direction of React is wrong?
Check compatibility of React with web components: https://custom-elements-everywhere.com/ It's not directly because of jsx, but because of synthetic "let's make it up" approach of React.
-
Regarding converting svelte file into pure js file
I have been using this approach recently as well, working great thus far ! Some things to consider though: - I would recommend checking if the other frameworks you intend to use have good web components support (looking at you, react): https://custom-elements-everywhere.com/ - There are ways to do so without web components, but I wouldn't recommend them unless your framework has poor web components support.
-
HTML with Superpowers: An Introduction to Web Components
VueJS actually fails some advanced tests for WebComponents: https://custom-elements-everywhere.com/
So, VueJS docs are actually incorrect when they say it scores 100%. The actual score is 90%.
I had reported this 8 months ago.
-
Building Web Components 101 - Part 1
Since Web Components are supported natively by browsers, they can be used in any libraries and frameworks either directly or with configurations. https://custom-elements-everywhere.com/ is a great site to check custom elements support status by different libraries and frameworks.
- Check if a library/framework supports the usage of custom elements
- custom-elements-everywhere.com: Check if a library/framework supports the usage of custom elements
feelback-integrations
-
Anyone want to collab on something?
Hi, I'm building Feelback, would like an hand to build the svelte integration. I did already for plain JS and React on this SDKs repo.
-
Anyone struggling with product documentation?
Are you twilling about internal private docs or internal source but public facing? Because for the latter I’m building Feelback where custom feedback systems can get a grasp on the user perception of the docs as content. I wrote the Case study of Stripe docs where I share some examples.
-
Architecture of an early stage SAAS
Hi, just published the technical architecture of Feelback. The article discusses design principles, tradeoffs and tricks used to build the launch architecture of a SAAS.
-
Plugin to receive user signals, like upvote buttons, reactions or feedback forms
Hi, I' building a little plugin to add 'Is this page useful?' upvote buttons (with optional feedback) to documentation websites.
-
[AskJS] Asking advice on monorepo setup with multiple frameworks
Hi, I'm developing several client SDKs for a website plugin, which require some integration with the common UI frameworks like React, Vue, Nextjs, ...
-
Asking for some guidance on a plugin for static websites
Hi, I made a little plugin to easily add - Like button or Emoji reaction for blog posts - Is this page useful? upvote widgets for documentation pages - Send feedback form to receive advices/error reporting from users
-
Asking advice on plugin integration allowing to receive any kind 'signal' or feedback from users
I built a react package on the repository.
-
Asking feedback on a monorepo with multi client packages for different web frameworks
Hi would like some feedback on a plugin allowing to receive user feedbacks about your website content. It allows to easily add: - Likes to blog posts - 'Is this page useful?' with up/down votes on documentation pages - Emoji reactions to sections, parts or comments - Send feedback form for tips or error reporting, with custom data
-
Plugin integration with different client frameworks
Hi, I'm building client libraries for a website plugin which allows to receive user signals about your website content.
What are some alternatives?
stencil - A toolchain for building scalable, enterprise-ready component systems on top of TypeScript and Web Component standards. Stencil components can be distributed natively to React, Angular, Vue, and traditional web developers from a single, framework-agnostic codebase.
mitosis - Write components once, run everywhere. Compiles to React, Vue, Qwik, Solid, Angular, Svelte, and more.
details-dialog-element - A modal dialog that's opened with <details>.
nextjs-feedback-template - Chat more effectively with your customers via email, right here on our website!
hybrids - Extraordinary JavaScript UI framework with unique declarative and functional architecture
astuto - A free, open source, self-hosted customer feedback tool 🦊
astro - The web framework for content-driven websites. ⭐️ Star to support our work!
clearflask - Listen to your users during product development with ClearFlask
web-vitals - Essential metrics for a healthy site.
npm-imported-packages-lens - A Visual Studio extension that displays links to NPM, Git Repo (GitHub/GitLab, etc.) and Homepage for an imported package in javascript and typescript files on hover.
vscode-webview-ui-toolkit - A component library for building webview-based extensions in Visual Studio Code.
webiny-js - Open-source serverless enterprise CMS. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.