Extensions for ReactJS in Visual Studio Code

Development quicker and life easier, install a number of the Visual Studio Extensions that square measure outlined below and create your development a lot of and a lot of power tools than the alternative.

Top 10 Extensions for ReactJs in VSCode are:

  • The Bracket Pair Colorizer extension.
  • The change-case extension.
  • The Code Spell Checker extension.
  • The Duplicate Selection extension.
  • The EditorConfig for VS Code extension.
  • The VSCode React Refactorextension.
  • The npm Intellisense extension.
  • The ESLint extension.
  • The ES7 React/Redux/GraphQL/React-Native snippetsextension.
  • The Prettier – Code formattedextension.

Bracket Pair Colorizer: This extension permits matching brackets to be known with colors. The user will outline the characters to match, and which colors to use. The main aim of this extension is to allow the matching brackets to be identified with colors.

change-case: It is a wrapper around node-change-case for Visual Studio Code. The main job is to quickly modify the case of this choice or current word. It also works with multiple cursors.

Code Spell Checker: It is a basic spell checker that works well with the camelCase code. It basically assists in catching the common spelling errors whereas keeping the number of false positives low.

Duplicate Selection: This extension brings Sublime-like duplication of designated text, it duplicates it inline, and not during a printing operation, just like the default behavior of VSCode.

EditorConfig for VS Code: This extension brings the EditorConfig and .editorconfig support to our VSCode. This plugin mains to override user or workspace settings with settings that are found in .editorconfig files.

VSCode React Refactor: This simple extension provides the refactor code actions for React developers. IT extracts the JSX element to file or function. It also supports the TypeScript and TSX syntax. This extension works well with the classes, functions, and arrow functions.

npm Intellisense: This is a plugin that will auto-complete all the npm modules import statements. All imports for npm modules get automatically handled by this extension.

ESLint: It integrates the ESLint into your VS Code system. The ESLint statically analyzes your code in order to quickly find problems.

ES7 React/Redux/GraphQL/React-Native snippets: This extension helps in providing the JavaScript and React/Redux related snippets in ES7 with Babel plugin options for your VS Code.

Prettier – Code formatter: It is a code formatted. This VS Code package is used to format your JavaScript/matter/CSS exploitation is prettier. It basically parses your code and re-printing it with its own rules.

IDE for reactjs

1. VS Code –

You can download VS code on Windows, Mac, Ubuntu, Debian, Red Hat, Fedora, and on SUSE, free of cost under the open-source of MIT license. It is popular among developers for providing all kinds of programming needs. React and VS code easily transformed into a compelling React IDE to enhance the productivity and speed of development using plugins.

vs-code

2. Atom –

Atom is another interesting and widely used ReactJS IDE. With 50K plus Github stars and more than 13k forks, this open-source IDE for ReactJS development brings varieties of features for an amazing development experience for users as well as for developers. It allows programmers to mangle each part of Atom according to their convenience even without tasting any configuration file.

atom

Windows, Mac, and Linux offer a wide range of applications and high-end support. Additionally, with auto-completion of syntax and inline indentation, mini-map features, it can be customized using Node.js based plugins to maximize functionality.

3. Reactide –

Reactide is the first ReactJS IDE which can be considered as a cross-platform for web application development. It just does not offer an integrated Node Server and custom simulator which eliminates the need for building unnecessary built-tool and server configurations, it renders the project in the browser instantly and provides hot module re-loading by default. This free tool can be downloaded from macOS, Windows and Debian.

reactide

4. Alloy Editor React –

This rich ReactJS IDE text editor gets used as a core component for several applications such as blogs, eCommerce administrator tools, and many more. It comprises smart toolbars that appear on the selected text depending on the different context functionality. It allows developers to add buttons or upload relevant images from clipboards or to drag from any other applications. Its amazing architecture enables programmers to paste rich text from web pages and preserve the formatting.

alloy-editor-react

5. Webstorm

This ReactJS IDE is a paid service but one of the most feature-rich IDE for ReactJS Development around the entire javascript ecosystem. Its ecosystem includes Cordova, React Native, Electron, NodeJS, and many more.

webstorm

JetBrains is a producer of Webstorm, and from the last 18 years, it has been proved as one of the best IDE for continuous product upgrades as well as customer support. Due to its regular product upgrades and support, most of the React.js Development Company relies on this.

6. Nuclide –

Developed by FaceBook, Nuclide works as a text editor for both React Native and ReactJS. However, now Facebook is no longer associated with this and does not offer any associated updates; still, it gets huge community support. Many developers have considered Nuclide as one of the best IDE reactJS technology due to its cross-platform support, autocomplete, inline indentation, build in debugging capabilities, and diagnosis capabilities.

nuclide

7. Sublime Text-3 –

It is another powerful integrated development programme which helps in various programming languages and frameworks. The sublime Text tool is a great option for those who do not want to scratch their head for anything else.

sublime-text-3

It has many plugins available to turn sublime into a feature-rich IDE for ReactJS Development. Plus, it can be used for enhancing development experience with ColorSublime, Babel, SublimeREPL, ColorPicker, React ES6 snippet, and many other technologies.

8. Rekit Studio –

Rekit is another ReactJS IDE, which basically focuses on developing apps using React. Along with IDE it also works as a toolkit that gets used for developing scalable applications utilizing React, react-router, and redux. A few basic features like refactoring, unit tests, code generation, support for Less and Sass, react-router, command-line tools etc. help in expanding its functionality.

rekit-studio

9. Brackets –

If you are looking for any lightweight, modern and powerful text editor which blends seamlessly with visual tools, Brackets is worth consideration for you. Brackets are produced from Adobe, and it is available under MIT license as free to use the tool. You can find a range of plugins available to enhance Brackets functionality using React components even without delving into the creative procedures. Brackets are specially crafted for web designers and front-end developers.

brackets

10. Deco IDE –

Many React.js development services found Deco IDE as the best IDE to react to native development. Earlier it was supported by macOS, but now it is not getting any regular updates from them. Originally it was a paid IDE reactJS, but since 2016 it is now free and open-source to use.

deco-ide

How to minify files using nodejs

 Minification can help your website load several times faster

In production, it is recommended to minify any JavaScript code that is included with your application. Minification can help your website load several times faster, especially as the size of your JavaScript source code grows.

Here’s one way to set it up:

  1. Install Node.js
  2. Run npm init -y in your project folder (don’t skip this step!)
  3. Run npm install terser

Now, to minify a file called like_button.js, run in the terminal:

npx terser -c -m -o like_button.min.js -- like_button.js

This will produce a file called like_button.min.js with the minified code in the same directory. If you’re typing this often, you can create an npm script to give this command a name.

how to check reactjs version

Open package.json file check react version under dependencies

{
  "name": "my-app",
  "version": "0.1.0",
  "private": true,
  "dependencies": {
    "@testing-library/jest-dom": "^5.14.1",
    "@testing-library/react": "^11.2.7",
    "@testing-library/user-event": "^12.8.3",
    "react": "^17.0.2",
    "react-dom": "^17.0.2",
    "react-scripts": "4.0.3",
    "web-vitals": "^1.1.2"
  },
  "scripts": {
    "start": "react-scripts start",
    "build": "react-scripts build",
    "test": "react-scripts test",
    "eject": "react-scripts eject"
  },
  "eslintConfig": {
    "extends": [
      "react-app",
      "react-app/jest"
    ]
  },
  "browserslist": {
    "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
  }
}

Accidentally ufw aws disable

Detach and fix the volume of the problem instance using another instance

  • Launch a new instance (recovery instance).
  • Stop the original instance (DO NOT TERMINATE)
  • Detach the volume (problem volume) from the original instance
  • Attached it to the recovery instance as /dev/sdf.
  • Login to the recovery instance via ssh/putty
  • Run sudo lsblk to display attached volumes and confirm the name of the problem volume. It usually begins with /dev/xvdf. Mine is /dev/xvdf1
  • Mount problem volume.
$ sudo mount /dev/xvdf1 /mnt
$ cd /mnt/etc/ufw

Open ufw configuration file

  $ sudo vim ufw.conf
  • Press i to edit the file.
  • Change ENABLED=yes to ENABLED=no
  • Type Ctrl-C and type :wq to save the file.
  • Display content of ufw conf file using the command below and ensure that ENABLED=yes has been changed to ENABLED=no
  $ sudo cat ufw.conf 

Unmount volume

 $ cd ~
 $ sudo umount /mnt
  • Detach problem volume from recovery instance and re-attach it to the original instance as /dev/sda1.
  • Start the original instance and you should be able to log back in.

If you have any problem please call me aws support – +91-9555699081

Accidentally ufw aws disable

1- Stop your instance

2- Go to Instance Settings -> View/Change user Data

Right click on your Stopped instance -> Instance Settings -> Edit User Data

3- Paste this on the option Modify user data as text and Save

Content-Type: multipart/mixed; boundary="//"
MIME-Version: 1.0
--//
Content-Type: text/cloud-config; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="cloud-config.txt"
#cloud-config
cloud_final_modules:
- [scripts-user, always]
--//
Content-Type: text/x-shellscript; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="userdata.txt"
#!/bin/bash
ufw disable
iptables -L
iptables -F
--//

4- Start your instance

How to manage Journal logs in ubuntu

Yes you can delete everything inside of /var/log/journal/* but do not delete the directory itself. You can also query journalctl to find out how much disk space it’s consuming:

$ journalctl --disk-usage
Journals take up 3.8G on disk.

You can control the size of this directory using this parameter in your /etc/systemd/journald.conf:

SystemMaxUse=50M

You can force a log rotation:

$ sudo systemctl kill --kill-who=main --signal=SIGUSR2 systemd-journald.service

NOTE: You might need to restart the logging service to force a log rotation, if the above signaling method does not do it. You can restart the service like so:

$ sudo systemctl restart systemd-journald.service

abrt logs

These files too under /var/cache/abrt-di/* can be deleted as well. The size of the log files here is controlled under:

$ grep -i size /etc/abrt/abrt.conf 
# Max size for crash storage [MiB] or 0 for unlimited
MaxCrashReportsSize = 1000

You can control the max size of /var/cache/abrt-di by changing the following in file, /etc/abrt/plugins/CCpp.conf:

DebugInfoCacheMB = 2000

NOTE: If not defined DebugInfoCacheMB defaults to 4000 (4GB).

What is the journal?

what is journal in ubuntu

Many modern file systems employ a journal including NTFS, Ext3/4, XFS, HFS+, and others. The journal helps with two things, avoiding file system corruption and speeding up recovery after a failure such as a power loss or system crash. There are two major components to a file system, the data and the metadata. The data is the contents of a file, image, video, documents, and ultimately it is what gives the file system it’s value. The metadata is what describes the structure of the filesystem including how files are named, stored in directories, access permissions, file modification times, and recording areas of the disk that are in use or are free to be allocated to other files as they grow or are created. If the metadata becomes corrupted because of a system crash, it could lead to further data loss/corruption. For example, part of the disk might be selected for allocation to a file, but if it’s not recorded correctly before a crash, it might be added to the file’s list of data blocks, but still in the list of free data blocks and allocated to a second file later on. Now, there are two files that are sharing the same data blocks/content.

The journal is a place on the disk reserved for recording changes to the file system. The exact details of what is being changed it written first to the journal located in a single location on disk, then, after the journal is updated, the changes are applied to the appropriate locations on the disk which might require several writes. One the updates are done, the journal entry is marked as complete. After a crash, the system only need to examine the journal for incomplete entries and complete them to fix the file system. This speeds recovery and ensures a change is made entirely or not at all. If a block is allocated to a growing file, it will be added to the file’s block list and also marked as in use.

Also, on file systems that support journalling, most often it’s only metadata journalling to preserve the structure, but not the data itself. Full data journalling is normally quite expensive and slow, but less crucial than metadata. It’s possible to enable for data as well if needed.

Also, to complete this, there are some file systems that don’t currently offer journalling including FAT32, exFAT, Ext2, and UDF. If there’s a crash during an update, a full scan of the filesystem needs to be done to track down any errors or corruption.