Aleksandr Filatov

How to use React Routing into Webview for VSCode extensions?

** Intro ** Recently I've faced with issue how to implement navigation between views into my VSCode extension based on ReactJS.

At first sight it looks that webview allows you to work into it like with web app into the browser. It actually is, but with some restrictions.

react-routing-dom

DOM bindings for React Router

I've started with 1st basic example but got failed because webview doesn't support URL into VSCode extensions.

So, I've got t great solution on SO. Instead of using links with navigation over URL you should use createMemoryHistory or MemoryRouter I've started to use the last one for myself.

See code example my the link to my blog

Optimize-js I will not describe this tool a lot here, because it's already good done by author on github

I just want to mention that this tool wrap up all immediately-invoked functions or likely-to-be-invoked functions in parentheses what is do a great optimization a JavaScript file for faster initial execution and parsing (based on my experience).

The performance of application where I've introduced optimize-js improved on 20% in a common (tested in Chrome and IE11).

• Clarification on Readme to the optimize-js
• Some of Nolan thoughts on the virtues of compile-time optimizations can be found in "Parens and Performance" – counterpost

Is it maintaining now? - Unfortunately, no (but feel free to send PR)

I've done some Hybrid Mobile apps with both technologies Apache Cordova and React Native and described my experience in my blog.

In a few words, I would suggest to use each technology in accordance what what is your current code base and what do you want to achieve.

React Native is a great option if you need that extra edge in performance with multi-threading and native UI rendering. Or you already have a web app based on React which you want to port to mobile.

On the other hand, if you have an existing web application code and you want to reuse some or all, including the ability to use web third-party libraries, then Cordova is the best option.

ProGuard is the most popular optimizer for Java bytecode. It makes your Java and Android applications up to 90% smaller and up to 20% faster. ProGuard also provides minimal protection against reverse engineering by obfuscating the names of classes, fields and methods.

I didn't find any plugins for it. So I've implemented it by myself and shared it on GitHub.

Feel free to use!

I could define the next points why we have to migrate:

• Decrease build time of our application. (It was the main cause).
• Also jspm install takes much more time than npm install.
• Many config files for SystemJS and JSPM. For Webpack you can use just one main config file, and you can use some separate config files for specific builds using inheritance and merge them.