I recently came across a bit of knowledge about Babel and got some interest in it, so I planned to take a look at the principle of Babel and then summarize it for learning, which is too complicated to write in multiple blogs.
In this week’s work, there is a requirement for me to generate a Decision Tree on the front end, so I went to investigate a lot of open source solutions. Here is the chart I investigated at the beginning. You can take a look and choose according to your own choice. Suitable, and finally I chose G6.
ActuallyG6的文档It’s already considered very good, so I have two main purposes for writing this blog:
Here to complain, G6 is too unfriendly for TypeScript, all properties are optional, and sometimes write down a bunch of question marks
Recently, I was interested in how to develop a VsCode plugin, so I deliberately read some plugin Development Documents, mainly looking at a中文翻译的文档However, this doc is not complete. It is basically a list of key functions, but it is very good to get started. However, if you want to go deeper, you still have to look英文的文档。
Most of the content is relatively simple, mainly configuration, it can take effect. What I want to summarize this time is how to develop a brand new language plugin. That is to say, if you want to define a new language similar to JSX, if you provide VsCode Support, such as syntax highlighting, code snippets, tag autism, error prompts, auto-completion, etc.
These few weeks is the massive open online course 400 ocean bought about React best engineering practices of the course to listen to the seventy-eight, the rest is mainly two parts, one part is some interactive optimization, and a little bit about performance optimization, these two parts I feel is not very urgent, can be in my work to slowly experience.
My current priority in React is that I have only learned practice, but I don’t know why I write a lot of things like this, such as why setState can be updated, how hooks take effect, what React fiber is, etc. I don’t understand these, I feel that my React is still floating in mid-air, and there is no better landing, so the next step is to understand the principle. As for whether to read the source code, let’s talk about it next.
The main content of this blog is to read the blogs of several bosses at home and abroad, and first have a general understanding of the fiber of react
In contact with the content of Redux, it is inevitable to contact some of its supporting tools, for a while by these tools to make some confusion, do not know which is which, their respective roles and connections. This article will simply record my query results.
First, let’s talk about these tools, redux, redux-thunk, redux-toolkit, react-redux.
This week, I need to develop an npm package in my work to supplement other existing pacakge. The entire repository adopts the form of monorepo to record the pitfalls and new technologies learned during the whole process
At present, there are more and more web IDE products running on the browser side. According to their functional characteristics, the current web IDE can be divided into two types. One is to migrate the functions of the local IDE basically intact. To the IDE on the web side, such as the most popular front-end IDE VS Code, with the help of cloud + containerization capabilities, VS Code has almost exactly the same functions as the local IDE on the browser side; there is also a web IDE that is more Focus on the presentation of’page development and real-time code parsing, compiling, and previewing ', and the implementation of code packaging and construction It is not limited to the implementation at the server level (such as based on Docker containers, etc.). Some products implement the functions of’compile, package, build, and run ‘based on browser-side code, and all of this is only based on our original development system.’ Local IDE + Node local build, local service + browser access preview 'has the ability. Representatives of such products are CodeSandbox, codepen, StackBlitz, JSFiddle, etc.
That is to say, the former just puts the code editing on the web segment. In fact, it uses the cloud to store the code, compile the project, package and run it, etc. In this way, what we finally get is no different from local development. The difference is that we don’t have to specially download an editor.
The latter is a part of the compile packaging function and the final run in the browser, and due to the limitations of the browser, the size of the application it can support is limited (PS: recently encountered a problem, see the error should be Code size exceeds 500K, leave a pit, leave it to be solved later, hehe)
The React team has focused on code reuse from the beginning
Their solutions to reuse code: Mixin, HOC, Render Prop, and now Custom Hook
Therefore, Custom Hook is not a product of a slap in the head, even many developers with rich development experience in Custom Hook do not understand how Hook came to be and what role it plays in React
It is impossible to deeply understand Custom Hook without understanding this design idea. Today we will learn together
Recently started to read some knowledge about react, and inevitably came into contact with redux.
I took a look at his doc to briefly summarize.
Note that most of the original content is outdated, because react updated the hook. I will go back and study what improvements react-redux has made to the hook, and then reexplain it. However, most of the content of this blog is about native redux, which can also be safely eaten.
Recently, when looking at some security knowledge, I found a new vulnerability called SSRF. The principle of this vulnerability is not complicated, but because it is the first time I have encountered it, I still simply record it.