Create Your Own Input Field with JavaScript Web Components

In today's video I'll show you how to build your own custom input field using web components. It'll support features such as adding an error message programmatically, and forwarding on some attributes.
🏫 My Udemy Courses - www.udemy.com/user/domenic-co...
🎨 Download my VS Code theme - marketplace.visualstudio.com/...
💜 Join my Discord Server - / discord
🐦 Find me on Twitter - / dcodeyt
💸 Support me on Patreon - / dcode
📰 Follow me on DEV Community - dev.to/dcodeyt
📹 Join this channel to get access to perks - / @dcode-software
If this video helped you out and you'd like to see more, make sure to leave a like and subscribe to dcode!
#dcode #javascript

Пікірлер: 15

  • @hoshi411
    @hoshi4112 ай бұрын

    you made another video on how to make a button web component and in this one you have made an input. Now please make a third video where you use the button.js file and the input.js file together in the same project and when you click on my-button element it updates my-input element. There have been many tutorials out there about building a single component but no one has put them together yet.

  • @kerrykreiter445
    @kerrykreiter4453 ай бұрын

    Super cool and useful! Thanks Dom!

  • @dcode-software

    @dcode-software

    3 ай бұрын

    Glad you liked it!

  • @vincent-cg7bl
    @vincent-cg7bl3 ай бұрын

    I discovered your channel with very good videos. Have you ever made a video on how to organize your folders and files when you have several components? From a performance point of view, maybe it's not a good practice to load them if you have a lot of them? A bit like Angular where everything is compiled.

  • @dcode-software

    @dcode-software

    3 ай бұрын

    Yeah, I've read some differing opinions when it comes to loading the components and CSS. I'm unsure of what the "correct" answer is, but for small-scale apps I don't see an issue - plus there's arguments to say that the browser will cache the resources (JS, CSS etc.) anyway so it may not be as big of a problem as originally thought.

  • @mpsbrasilia
    @mpsbrasilia3 ай бұрын

    Sou seu fã, sou do Brasil.

  • @mpsbrasilia
    @mpsbrasilia3 ай бұрын

    Crie um sidebar, chamando os componentes em uma div contente. Obrigado.

  • @user-lp4nb4vk5r
    @user-lp4nb4vk5r2 ай бұрын

    nice video

  • @smoothbeak
    @smoothbeak3 ай бұрын

    Looks good to me. Is there/what are the advantages to going this route rather than using a framework like React?

  • @dcode-software

    @dcode-software

    3 ай бұрын

    In small apps I don't see a problem with web components if that's what you want to do, but for medium/large scale I would stick with React. Of course, React offers a lot of functionality that web components aren't able to provide without a library/custom code. There's more to it than just component-based UI.

  • @smoothbeak

    @smoothbeak

    3 ай бұрын

    @@dcode-softwareCheers

  • @mhsn27mhsn10
    @mhsn27mhsn103 ай бұрын

    hello , can use tailwindcss class with when create web components or just need to pure css ?

  • @dcode-software

    @dcode-software

    3 ай бұрын

    Hey, I haven't tried Tailwind CSS with web components but I would imagine it would work as long as the Tailwind classes are available for the component to use.

  • @jonice4229
    @jonice42293 ай бұрын

    i think Light dom is better than shadow dom just in case javascript is disabled

  • @mpsbrasilia
    @mpsbrasilia3 ай бұрын

    Show show show