Avav Smith

Avav Smith


Build WAI-ARIA compliant React autocomplete components


Primitives to build simple, flexible, WAI-ARIA compliant React autocomplete/dropdown/select/combobox components

The problem

You need an autocomplete/dropdown/select experience in your application and you want it to be accessible. You also want it to be simple and flexible to account for your use cases.

This solution

This is a component that controls user interactions and state for you so you can create autocomplete/dropdown/select/etc. components. It uses a render prop which gives you maximum flexibility with a minimal API because you are responsible for the rendering of everything and you simply apply props to what you’re rendering.

This differs from other solutions which render things for their use case and then expose many options to allow for extensibility resulting in a bigger API that is less flexible as well as making the implementation more complicated and harder to contribute to.

This module is distributed via npm which is bundled with node and should be installed as one of your project’s dependencies:

npm install --save downshift


import Downshift from 'downshift'

function BasicAutocomplete({items, onChange}) {
  return (
      }) => (
          <input {...getInputProps({placeholder: 'Favorite fruit ?'})} />
          {isOpen ? (
            <div style={{border: '1px solid #ccc'}}>
                  i =>
                    !inputValue ||
                .map((item, index) => (
                        highlightedIndex === index ? 'gray' : 'white',
                      fontWeight: selectedItem === item ? 'bold' : 'normal',
          ) : null}

function App() {
  return (
      items={['apple', 'orange', 'carrot']}
      onChange={selectedItem => console.log(selectedItem)}

downshift is the only component. It doesn’t render anything itself, it just
calls the render function and renders that. [“Use a render
prop!”][use-a-render-prop]! <Downshift render={/* your JSX here! */} />.



any | defaults to null

Pass an item or an array of items that should be selected by default.


number/null | defaults to null

This is the initial index to highlight when the menu first opens.


string | defaults to ''

This is the initial input value.


boolean | defaults to false

This is the initial isOpen value.


function(item: any) | defaults to: i => (i == null ? '' : String(i))

Used to determine the string value for the selected item (which is used to
compute the inputValue).


function(prevItem: any, item: any) | defaults to: (prevItem, item) => (prevItem !== item)

Used to determine if the new selectedItem has changed compared to the previous
selectedItem and properly update Downshift’s internal state.


function({/* see below */}) | default messages provided in English

This function is passed as props to a Status component nested within and
allows you to create your own assertive ARIA statuses.

A default getA11yStatusMessage function is provided that will check
resultCount and return “No results.” or if there are results but no item is
highlighted, “resultCount results are available, use up and down arrow keys to
navigate.” If an item is highlighted it will run itemToString(highlightedItem)
and display the value of the highlightedItem.

The object you are passed to generate your status message has the following

property type description
highlightedIndex number/null The currently highlighted index
highlightedItem any The value of the highlighted item
inputValue string The current input value
isOpen boolean The isOpen state
itemToString function(any) The itemToString function (see props) for getting the string value from one of the options
previousResultCount number The total items showing in the dropdown the last time the status was updated
resultCount number The total items showing in the dropdown
selectedItem any The value of the currently selected item


function(selectedItem: any, stateAndHelpers: object) | optional, no useful

Called when the user selects an item and the selected item has changed. Called
with the item that was selected and the new state of downshift. (see
onStateChange for more info on stateAndHelpers).

  • selectedItem: The item that was just selected
  • stateAndHelpers: This is the same thing your render prop function is
    called with (see Render Prop Function)


function(selectedItem: any, stateAndHelpers: object) | optional, no useful

Called when the user selects an item, regardless of the previous selected item.
Called with the item that was selected and the new state of downshift. (see
onStateChange for more info on stateAndHelpers).

  • selectedItem: The item that was just selected
  • stateAndHelpers: This is the same thing your render prop function is
    called with (see Render Prop Function)


function(changes: object, stateAndHelpers: object) | optional, no useful

This function is called anytime the internal state changes. This can be useful
if you’re using downshift as a “controlled” component, where you manage some or
all of the state (e.g. isOpen, selectedItem, highlightedIndex, etc) and then
pass it as props, rather than letting downshift control all its state itself.
The parameters both take the shape of internal state ({highlightedIndex: number, inputValue: string, isOpen: boolean, selectedItem: any}) but differ

  • changes: These are the properties that actually have changed since the last
    state change. This also has a type property which you can learn more about
    in the stateChangeTypes section.
  • stateAndHelpers: This is the exact same thing your render prop function is
    called with (see Render Prop Function)

Tip: This function will be called any time any state is changed. The best
way to determine whether any particular state was changed, you can use


function(state: object, changes: object) | optional

🚨 This is a really handy power feature 🚨

This function will be called each time downshift sets its internal state
(or calls your onStateChange handler for control props). It allows you to
modify the state change that will take place which can give you fine grain
control over how the component interacts with user updates without having to
use Control Props. It gives you the current state and the
state that will be set, and you return the state that you want to set.

  • state: The full current state of downshift.
  • changes: These are the properties that are about to change. This also has a
    type property which you can learn more about in the
    stateChangeTypes section.
const ui = (
  <Downshift stateReducer={stateReducer}>{/* your callback */}</Downshift>

function stateReducer(state, changes) {
  // this prevents the menu from being closed when the user
  // selects an item with a keyboard or mouse
  switch (changes.type) {
    case Downshift.stateChangeTypes.keyDownEnter:
    case Downshift.stateChangeTypes.clickItem:
      return {
        isOpen: state.isOpen,
        highlightedIndex: state.highlightedIndex,
      return changes


function(inputValue: string, stateAndHelpers: object) | optional, no useful

Called whenever the input value changes. Useful to use instead or in combination
of onStateChange when inputValue is a controlled prop to
avoid issues with cursor positions.

  • inputValue: The current value of the input
  • stateAndHelpers: This is the same thing your render prop function is
    called with (see Render Prop Function)


number | optional, defaults the number of times you call getItemProps

This is useful if you’re using some kind of virtual listing component for
“windowing” (like


number | control prop (read more about this in the “Control Props”
section below)

The index that should be highlighted


string | control prop (read more about this in the “Control Props”
section below)

The value the input should have


boolean | control prop (read more about this in the “Control Props”
section below)

Whether the menu should be considered open or closed. Some aspects of the
downshift component respond differently based on this value (for example, if
isOpen is true when the user hits “Enter” on the input field, then the item at
the highlightedIndex item is selected).


any/Array(any) | control prop (read more about this in the “Control
Props” section below)

The currently selected item.


function({}) | required

This is called with an object. Read more about the properties of this object in
the section “Render Prop Function”.


string | defaults to a generated ID

You should not normally need to set this prop. It’s only useful if you’re server
rendering items (which each have an id prop generated based on the downshift
id). For more information see the FAQ below.


window | defaults to window

You should not normally need to set this prop. It’s only useful if you’re
rendering into a different window context from where your JavaScript is
running, for example an iframe.


function | optional

A helper callback to help control internal state of downshift like isOpen as
mentioned in this issue. The
same behavior can be achieved using onStateChange, but this prop is provided
as a helper because it’s a fairly common use-case if you’re controlling the
isOpen state:

const ui = (
    onOuterClick={() => this.setState({menuIsOpen: false})}
    {/* your callback */}

This callback will only be called if isOpen is true.


There are a few props that expose changes to state
(onStateChange and stateReducer).
For you to make the most of these APIs, it’s important for you to understand
why state is being changed. To accomplish this, there’s a type property on the
changes object you get. This type corresponds to a
Downshift.stateChangeTypes property. If you want to see what change types
are available, run this in your app:


Control Props

downshift manages its own state internally and calls your onChange and
onStateChange handlers with any relevant changes. The state that downshift
manages includes: isOpen, selectedItem, inputValue, and
highlightedIndex. Your render prop function (read more below) can be used to
manipulate this state from within the render function and can likely support
many of your use cases.

However, if more control is needed, you can pass any of these pieces of state as
a prop (as indicated above) and that state becomes controlled. As soon as
this.props[statePropKey] !== undefined, internally, downshift will determine
its state based on your prop’s value rather than its own internal state. You
will be required to keep the state up to date (this is where onStateChange
comes in really handy), but you can also control the state from anywhere, be
that state from other components, redux, react-router, or anywhere else.

Note: This is very similar to how normal controlled components work elsewhere
in react (like <input />). If you want to learn more about this concept, you
can learn about that from this the [“Controlled Components”
lecture][controlled-components-lecture] and exercises from [React
Training’s][react-training] [Advanced React][advanced-react] course.

Render Prop Function

This is where you render whatever you want to based on the state of downshift.
It’s a regular prop called render: <Downshift render={/* right here*/} />.

You can also pass it as the children prop if you prefer to do things that way
<Downshift>{/* right here*/}</Downshift>

The properties of this object can be split into three categories as indicated

prop getters

the blog post about prop getters

These functions are used to apply props to the elements that you render. This
gives you maximum flexibility to render what, when, and wherever you like. You
call these on the element in question (for example: <input {...getInputProps()})). It’s advisable to pass all your props to that function
rather than applying them on the element yourself to avoid your props being
overridden (or overriding the props returned). For example:
getInputProps({onKeyUp(event) {console.log(event)}}).

property type description
getToggleButtonProps function({}) returns the props you should apply to any menu toggle button element you render.
getInputProps function({}) returns the props you should apply to the input element that you render.
getItemProps function({}) returns the props you should apply to any menu item elements you render.
getLabelProps function({}) returns the props you should apply to the label element that you render.
getRootProps function({},{}) returns the props you should apply to the root element that you render. It can be optional.


Most of the time, you can just render a div yourself and Downshift will
apply the props it needs to do its job (and you don’t need to call this
function). However, if you’re rendering a composite component (custom component)
as the root element, then you’ll need to call getRootProps and apply that to
your root element.

Required properties:

  • refKey: if you’re rendering a composite component, that component will need
    to accept a prop which it forwards to the root DOM element. Commonly, folks
    call this innerRef. So you’d call: getRootProps({refKey: 'innerRef'}) and
    your composite component would forward like: <div ref={props.innerRef} />

If you’re rendering a composite component, Downshift checks that
getRootProps is called and that refKey is a prop of the returned composite
component. This is done to catch common causes of errors but, in some cases, the
check could fail even if the ref is correctly forwarded to the root DOM
component. In these cases, you can provide the object {suppressRefError : true} as the second argument to getRootProps to completely bypass the check.
Please use it with extreme care and only if you are absolutely sure that the ref
is correctly forwarded otherwise Downshift will unexpectedly fail.

See #235 for the discussion that lead to this.


This method should be applied to the input you render. It is recommended that
you pass all props as an object to this method which will compose together any
of the event handlers you need to apply to the input while preserving the ones
that downshift needs to apply to make the input behave.

There are no required properties for this method.

Optional properties:

  • disabled: If this is set to true, then no event handlers will be returned from getInputProps and a disabled prop will be returned (effectively disabling the input).


This method should be applied to the label you render. It is useful for
ensuring that the for attribute on the <label> (htmlFor as a react prop)
is the same as the id that appears on the input. If no htmlFor is provided
then an ID will be generated and used for the input and the label for

There are no required properties for this method.

Note: You can definitely get by without using this (just provide an id to
your input and the same htmlFor to your label and you’ll be good with
accessibility). However, we include this so you don’t forget and it makes
things a little nicer for you. You’re welcome 😀


The props returned from calling this function should be applied to any menu
items you render.

This is an impure function, so it should only be called when you will
actually be applying the props to an item.

details summaryWhat do you mean by impure function?

Basically just don’t do this:

items.map(item => {
  const props = getItemProps({item}) // we're calling it here
  if (!shouldRenderItem(item)) {
    return null // but we're not using props, and downshift thinks we are...
  return <div {...props} />

Instead, you could do this:

items.filter(shouldRenderItem).map(item => <div {...getItemProps({item})} />)

Required properties:

  • item: this is the item data that will be selected when the user selects a
    particular item.

Optional properties:

  • index: This is how downshift keeps track of your item when updating the
    highlightedIndex as the user keys around. By default, downshift will
    assume the index is the order in which you’re calling getItemProps. This
    is often good enough, but if you find odd behavior, try setting this
    explicitly. It’s probably best to be explicit about index when using a
    windowing library like react-virtualized.
  • disabled: If this is set to true, then all of the downshift item event
    handlers will be omitted. Items will not be highlighted when hovered,
    and items will not be selected when clicked.


Call this and apply the returned props to a button. It allows you to toggle
the Menu component. You can definitely build something like this yourself (all
of the available APIs are exposed to you), but this is nice because it will also
apply all of the proper ARIA attributes.

Optional properties:

  • disabled: If this is set to true, then all of the downshift button event
    handlers will be omitted (it wont toggle the menu when clicked).
  • aria-label: The aria-label prop is in English. You should probably override
    this yourself so you can provide translations:
const myButton = (
      'aria-label': translateWithId(isOpen ? 'close.menu' : 'open.menu'),


These are functions you can call to change the state of the downshift component.

property type description
clearSelection function(cb: Function) clears the selection
clearItems function() Clears downshift’s record of all the items. Only really useful if you render your items asynchronously within downshift. See #186
closeMenu function(cb: Function) closes the menu
openMenu function(cb: Function) opens the menu
selectHighlightedItem function(otherStateToSet: object, cb: Function) selects the item that is currently highlighted
selectItem function(item: any, otherStateToSet: object, cb: Function) selects the given item
selectItemAtIndex function(index: number, otherStateToSet: object, cb: Function) selects the item at the given index
setHighlightedIndex function(index: number, otherStateToSet: object, cb: Function) call to set a new highlighted index
toggleMenu function(otherStateToSet: object, cb: Function) toggle the menu open state
reset function(otherStateToSet: object, cb: Function) this resets downshift’s state to a reasonable default
setItemCount function(count: number) this sets the itemCount. Handy in situations where you’re using windowing and the items are loaded asynchronously from within downshift (so you can’t use the itemCount prop.
unsetItemCount function() this unsets the itemCount which means the item count will be calculated instead by the itemCount prop or based on how many times you call getItemProps.
setState function(stateToSet: object, cb: Function) This is a general setState function. It uses downshift’s internalSetState function which works with control props and calls your onSelect, onChange, etc. (Note, you can specify a type which you can reference in some other APIs like the stateReducer).

otherStateToSet refers to an object to set other internal state. It is
recommended to avoid abusing this, but is available if you need it.


These are values that represent the current state of the downshift component.

property type description
highlightedIndex number / null the currently highlighted item
inputValue string / null the current value of the getInputProps input
isOpen boolean the menu open state
selectedItem any the currently selected item input


As a convenience, the id and itemToString props which you pass to
<Downshift /> are available here as well.

Event Handlers

Downshift has a few events for which it provides implicit handlers. Several of
these handlers call event.preventDefault(). Their additional functionality is
described below.

default handlers

  • ArrowDown: moves the highlighted index down by 1. If this shift key is held
    when this event fires, the highlighted index will jump down 5 indices instead of 1.
    NOTE: if the current highlighed index is within the bottom 5 indices, the top-most
    index will be highlighted.)

  • ArrowUp: moves the highlighted index up by 1. If this shift key is held when
    this event fires, the highlighted index will jump up 5 indices instead of 1. NOTE:
    if the current highlighed index is within the top 5 indices, the bottom-most index
    will be highlighted.)

  • Enter: if the menu is open, select the currently highlighted item. If the menu
    is open, the usual ‘Enter’ event is prevented by Downshift’s default implicit enter
    handler; so, for example, a form submission event will not work as one might expect
    (though if the menu is closed the form submission will work normally). See below
    for customizing the handlers.

  • Escape: will reset downshift’s state. This means that highlightedIndex will be
    set to the defaultHighlightedIndex, the inputValue will be set to the itemToString
    value of the selectedItem, and the isOpen state will be set to false.

customizing handlers

You can provide your own event handlers to Downshift which will be called before the default handlers:

const ui = (
    {({getInputProps}) => (
          onKeyDown: event => {
            // your handler code

If you would like to prevent the default handler behavior in some cases, you can set the event’s preventDownshiftDefault property to true:

const ui = (
    {({getInputProps}) => (
          onKeyDown: event => {
            if (event.key === 'Enter') {
              // Prevent Downshift's default 'Enter' behavior.
              event.preventDownshiftDefault = true

              // your handler code

If you would like to completely override Downshift’s behavior for a handler, in favor of your own, you can bypass prop getters:

const ui = (
    {({getInputProps}) => (
        onKeyDown={event => {
          // your handler code



Allows reseting the internal id counter which is used to generate unique ids for Downshift component.

You should never need to use this in the browser. Only if you are running an universal React app that is rendered on the server you should call resetIdCounter before every render so that the ids that get generated on the server match the ids generated in the browser.

import Downshift from 'downshift';


React Native

Since Downshift renders it’s UI using render props, Downshift supports rendering on React Native with ease. Use components like <View>, <Text>, <TouchableOpacity> and others inside of your render method to generate awesome autocomplete, dropdown, or selection components.


  • Your root view will need to either pass a ref to getRootProps or call getRootProps with { suppressRefError: true }. This ref is used to catch a common set of errors around composite components. Learn more in getRootProps.
  • When using a <FlatList> or <ScrollView>, be sure to supply the keyboardShouldPersistTaps prop to ensure that your text input stays focus, while allowing for taps on the touchables rendered for your items.

Download Details:

Author: downshift

Live Demo: http://downshift.netlify.com/

GitHub: https://github.com/downshift-js/downshift

#reactjs #javascript

What is GEEK

Buddha Community

Build WAI-ARIA compliant React autocomplete components
Autumn  Blick

Autumn Blick


How native is React Native? | React Native vs Native App Development

If you are undertaking a mobile app development for your start-up or enterprise, you are likely wondering whether to use React Native. As a popular development framework, React Native helps you to develop near-native mobile apps. However, you are probably also wondering how close you can get to a native app by using React Native. How native is React Native?

In the article, we discuss the similarities between native mobile development and development using React Native. We also touch upon where they differ and how to bridge the gaps. Read on.

A brief introduction to React Native

Let’s briefly set the context first. We will briefly touch upon what React Native is and how it differs from earlier hybrid frameworks.

React Native is a popular JavaScript framework that Facebook has created. You can use this open-source framework to code natively rendering Android and iOS mobile apps. You can use it to develop web apps too.

Facebook has developed React Native based on React, its JavaScript library. The first release of React Native came in March 2015. At the time of writing this article, the latest stable release of React Native is 0.62.0, and it was released in March 2020.

Although relatively new, React Native has acquired a high degree of popularity. The “Stack Overflow Developer Survey 2019” report identifies it as the 8th most loved framework. Facebook, Walmart, and Bloomberg are some of the top companies that use React Native.

The popularity of React Native comes from its advantages. Some of its advantages are as follows:

  • Performance: It delivers optimal performance.
  • Cross-platform development: You can develop both Android and iOS apps with it. The reuse of code expedites development and reduces costs.
  • UI design: React Native enables you to design simple and responsive UI for your mobile app.
  • 3rd party plugins: This framework supports 3rd party plugins.
  • Developer community: A vibrant community of developers support React Native.

Why React Native is fundamentally different from earlier hybrid frameworks

Are you wondering whether React Native is just another of those hybrid frameworks like Ionic or Cordova? It’s not! React Native is fundamentally different from these earlier hybrid frameworks.

React Native is very close to native. Consider the following aspects as described on the React Native website:

  • Access to many native platforms features: The primitives of React Native render to native platform UI. This means that your React Native app will use many native platform APIs as native apps would do.
  • Near-native user experience: React Native provides several native components, and these are platform agnostic.
  • The ease of accessing native APIs: React Native uses a declarative UI paradigm. This enables React Native to interact easily with native platform APIs since React Native wraps existing native code.

Due to these factors, React Native offers many more advantages compared to those earlier hybrid frameworks. We now review them.

#android app #frontend #ios app #mobile app development #benefits of react native #is react native good for mobile app development #native vs #pros and cons of react native #react mobile development #react native development #react native experience #react native framework #react native ios vs android #react native pros and cons #react native vs android #react native vs native #react native vs native performance #react vs native #why react native #why use react native

Aubrey  Price

Aubrey Price


Build a simple React Native Pokemon app with React-Navigation

As we start learning new technologies we want to start building something or work on a simple project to get a better understanding of the technology. So, let’s build this simple app.
For this app, we will be using PokeApi to get our pokemon data, and also we will be using Hooks. I am using pokemondb for pokemon sprites. It’s just a personal preference you can use whatever you want.

#react-native #react-native-app #react-navigation #react-native-development #react

Mathew Rini


How to Select and Hire the Best React JS and React Native Developers?

Since March 2020 reached 556 million monthly downloads have increased, It shows that React JS has been steadily growing. React.js also provides a desirable amount of pliancy and efficiency for developing innovative solutions with interactive user interfaces. It’s no surprise that an increasing number of businesses are adopting this technology. How do you select and recruit React.js developers who will propel your project forward? How much does a React developer make? We’ll bring you here all the details you need.

What is React.js?

Facebook built and maintains React.js, an open-source JavaScript library for designing development tools. React.js is used to create single-page applications (SPAs) that can be used in conjunction with React Native to develop native cross-platform apps.

React vs React Native

  • React Native is a platform that uses a collection of mobile-specific components provided by the React kit, while React.js is a JavaScript-based library.
  • React.js and React Native have similar syntax and workflows, but their implementation is quite different.
  • React Native is designed to create native mobile apps that are distinct from those created in Objective-C or Java. React, on the other hand, can be used to develop web apps, hybrid and mobile & desktop applications.
  • React Native, in essence, takes the same conceptual UI cornerstones as standard iOS and Android apps and assembles them using React.js syntax to create a rich mobile experience.

What is the Average React Developer Salary?

In the United States, the average React developer salary is $94,205 a year, or $30-$48 per hour, This is one of the highest among JavaScript developers. The starting salary for junior React.js developers is $60,510 per year, rising to $112,480 for senior roles.

* React.js Developer Salary by Country

  • United States- $120,000
  • Canada - $110,000
  • United Kingdom - $71,820
  • The Netherlands $49,095
  • Spain - $35,423.00
  • France - $44,284
  • Ukraine - $28,990
  • India - $9,843
  • Sweden - $55,173
  • Singapore - $43,801

In context of software developer wage rates, the United States continues to lead. In high-tech cities like San Francisco and New York, average React developer salaries will hit $98K and $114per year, overall.

However, the need for React.js and React Native developer is outpacing local labour markets. As a result, many businesses have difficulty locating and recruiting them locally.

It’s no surprise that for US and European companies looking for professional and budget engineers, offshore regions like India are becoming especially interesting. This area has a large number of app development companies, a good rate with quality, and a good pool of React.js front-end developers.

As per Linkedin, the country’s IT industry employs over a million React specialists. Furthermore, for the same or less money than hiring a React.js programmer locally, you may recruit someone with much expertise and a broader technical stack.

How to Hire React.js Developers?

  • Conduct thorough candidate research, including portfolios and areas of expertise.
  • Before you sit down with your interviewing panel, do some homework.
  • Examine the final outcome and hire the ideal candidate.

Why is React.js Popular?

React is a very strong framework. React.js makes use of a powerful synchronization method known as Virtual DOM, which compares the current page architecture to the expected page architecture and updates the appropriate components as long as the user input.

React is scalable. it utilises a single language, For server-client side, and mobile platform.

React is steady.React.js is completely adaptable, which means it seldom, if ever, updates the user interface. This enables legacy projects to be updated to the most new edition of React.js without having to change the codebase or make a few small changes.

React is adaptable. It can be conveniently paired with various state administrators (e.g., Redux, Flux, Alt or Reflux) and can be used to implement a number of architectural patterns.

Is there a market for React.js programmers?
The need for React.js developers is rising at an unparalleled rate. React.js is currently used by over one million websites around the world. React is used by Fortune 400+ businesses and popular companies such as Facebook, Twitter, Glassdoor and Cloudflare.

Final thoughts:

As you’ve seen, locating and Hire React js Developer and Hire React Native developer is a difficult challenge. You will have less challenges selecting the correct fit for your projects if you identify growing offshore locations (e.g. India) and take into consideration the details above.

If you want to make this process easier, You can visit our website for more, or else to write a email, we’ll help you to finding top rated React.js and React Native developers easier and with strives to create this operation

#hire-react-js-developer #hire-react-native-developer #react #react-native #react-js #hire-react-js-programmer

Kaustav Hazra


 Component Life Cycle in React

Every component in React goes through a lifecycle of events. You can think is of going through a cycle of birth, growth, and death the same as the picture below.

The phases are:

  • Initialization — Starting the journey of your component
  • Mounting — Birth of your component
  • Update — Growth of your component
  • Unmount — Death of your component

1. Initialization

This is the phase in which the component is going to start its journey. The developer has to define the props and initial state of the component. This is usually done inside the constructor method (see below to understand the initialization phase better).

#react #react-lifecycle-method #react-course #react-for-beginner #react-js-tutorials

Anda Lacacima

Anda Lacacima


How to Build React Component using React, React DOM and Babel

Now Let’s start discussing today’s topic.Today we’ll discuss about basic things you must know about React Library.It’s a famous front-end library which use in IT industry for business applications.Also day by day it’s getting updated.So, It will be much important for you to keep in touch with this library if you are willing/doing a_ job in IT industry _as it’s already a trending front-end technology now a days.So we’ll discuss it in details now and create your first React Component.

What is React ?

Simply, React is a JavaScript library that use to create _User Interfaces which runs on browsers _which was created by** Facebook._(one of the most popular ones, with over 100,000 stars on GitHub). It is the _view_ layer of an _MVC application**_ (Model View Controller)_

NOTE: React is not a framework.It’s a JavaScript library.

For a business application(client application) to be extremely successful it must be maintainable,manageable and_ re-usable.__Because when the business is expanding and when the customers asking for more improvement/changes the development team must be much responsible for making quick changes in the client application as soon as possible.That’s a more than 100% truth in _IT industry.So you must be a fast learner and a fast adapter when client requests rapid and complex changes in your business application.

Does React helps to overcome implementation complexity of client’s business applications

Yes.This is the most valuable and important thing which helps you when implementing a complex business application.React uses a concept called_ re-usable component__ which you may feel much comfortable with.It makes you re-use the same code in several places.Only thing you need to do is make changes to your props and __states.Using tiny components you could build your complex application in a simple way. __Also as this is a view part of the application it doesn’t depend(isolated with) on the _server state.

Components_ are like custom, reusable HTML elements, to quickly and efficiently build__ user interfaces_

_Now it’s time to try this with your own.I’m used _this online editor.It shows HTML, CSS, JavaScript sections clearly and separately.I recommend you to use it to make your first _React Component.

_We’ll create a simple HTML element which displays name and age of a __Person _using CSS styling as below(Image shows how a Person Component used to display information of two persons called Sanath and Pramod);

Image for post


You only need both HTML,CSS files below to implement Person component using HTML and CSS.Use below code in editor to try this.

#components #react-dom #programming #react #babel