Skip to content

added hindi translation for js environment requirement #47

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 14, 2019
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions content/blog/2019-08-15-new-react-devtools.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@ author: [bvaughn]
---
We are excited to announce a new release of the React Developer Tools, available today in Chrome, Firefox, and (Chromium) Edge!

## What's changed?
## What's changed? {#whats-changed}

A lot has changed in version 4!
At a high level, this new version should offer significant performance gains and an improved navigation experience.
Expand All @@ -14,7 +14,7 @@ It also offers full support for React Hooks, including inspecting nested objects

[Visit the interactive tutorial](https://react-devtools-tutorial.now.sh/) to try out the new version or [see the changelog](https://github.com/facebook/react/blob/master/packages/react-devtools/CHANGELOG.md#400-august-15-2019) for demo videos and more details.

## Which versions of React are supported?
## Which versions of React are supported? {#which-versions-of-react-are-supported}

**`react-dom`**

Expand All @@ -26,7 +26,7 @@ It also offers full support for React Hooks, including inspecting nested objects
* `0`-`0.61`: Not supported
* `0.62`: Will be supported (when 0.62 is released)

## How do I get the new DevTools?
## How do I get the new DevTools? {#how-do-i-get-the-new-devtools}

React DevTools is available as an extension for [Chrome](https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en) and [Firefox](https://addons.mozilla.org/en-US/firefox/addon/react-devtools/).
If you have already installed the extension, it should update automatically within the next couple of hours.
Expand All @@ -37,14 +37,14 @@ If you use the standalone shell (e.g. in React Native or Safari), you can instal
npm install -g react-devtools@^4
```

## Where did all of the DOM elements go?
## Where did all of the DOM elements go? {#where-did-all-of-the-dom-elements-go}

The new DevTools provides a way to filter components from the tree to make it easier to navigate deeply nested hierarchies.
Host nodes (e.g. HTML `<div>`, React Native `<View>`) are *hidden by default*, but this filter can be disabled:

![DevTools component filters](../images/blog/devtools-component-filters.gif)

## How do I get the old version back?
## How do I get the old version back? {#how-do-i-get-the-old-version-back}

If you are working with React Native version 60 (or older) you can install the previous release of DevTools from NPM:

Expand All @@ -70,7 +70,7 @@ yarn build:extension
# Follow the on-screen instructions to complete installation
```

## Thank you!
## Thank you! {#thank-you}

We'd like to thank everyone who tested the early release of DevTools version 4.
Your feedback helped improve this initial release significantly.
Expand Down
10 changes: 5 additions & 5 deletions content/docs/reference-javascript-environment-requirements.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
id: javascript-environment-requirements
title: JavaScript Environment Requirements
title: जावास्क्रिप्ट पर्यावरण आवश्यकताएँ
layout: docs
category: Reference
permalink: docs/javascript-environment-requirements.html
---

React 16 depends on the collection types [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) and [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set). If you support older browsers and devices which may not yet provide these natively (e.g. IE < 11) or which have non-compliant implementations (e.g. IE 11), consider including a global polyfill in your bundled application, such as [core-js](https://github.com/zloirock/core-js) or [babel-polyfill](https://babeljs.io/docs/usage/polyfill/).
React 16 संग्रह के प्रकार पर निर्भर करता है [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) और [Set](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set)। यदि आप पुराने ब्राउज़रों और उपकरणों का समर्थन करते हैं, जो अभी तक ये मूल रूप से प्रदान नहीं कर सकते हैं (जैसे IE <11) या जिनके पास गैर-अनुरूप कार्यान्वयन हैं (उदाहरण IE 11), तो अपने बंडल किए गए एप्लिकेशन में एक वैश्विक polyfill शामिल करें, जैसे कि [core-js](https://github.com/zloirock/core-js) या [babel-polyfill](https://babeljs.io/docs/usage/polyfill/)

A polyfilled environment for React 16 using core-js to support older browsers might look like:
पुराने ब्राउज़र का समर्थन करने के लिए core-js का उपयोग करके React 16 के लिए एक polyfilled वातावरण ऐसा दिख सकता है:

```js
import 'core-js/es/map';
Expand All @@ -23,8 +23,8 @@ ReactDOM.render(
);
```

React also depends on `requestAnimationFrame` (even in test environments).
You can use the [raf](https://www.npmjs.com/package/raf) package to shim `requestAnimationFrame`:
React `requestAnimationFrame` पर भी निर्भर करती है (परीक्षण वातावरण में भी)।
आप `requestAnimationFrame` के समर्थन के लिए [raf](https://www.npmjs.com/package/raf) package का उपयोग कर सकते हैं :

```js
import 'raf/polyfill';
Expand Down
4 changes: 2 additions & 2 deletions content/docs/reference-profiler.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ Its purpose is to help identify parts of an application that are slow and may be
> To opt into production profiling, React provides a special production build with profiling enabled.
> Read more about how to use this build at [fb.me/react-profiling](https://fb.me/react-profiling)

## Usage
## Usage {#usage}

A `Profiler` can be added anywhere in a React tree to measure the cost of rendering that part of the tree.
It requires two props: an `id` (string) and an `onRender` callback (function) which React calls any time a component within the tree "commits" an update.
Expand Down Expand Up @@ -70,7 +70,7 @@ render(
>
> Although `Profiler` is a light-weight component, it should be used only when necessary; each use adds some CPU and memory overhead to an application.

## `onRender` Callback
## `onRender` Callback {#onrender-callback}

The `Profiler` requires an `onRender` function as a prop.
React calls this function any time a component within the profiled tree "commits" an update.
Expand Down