When I tried to use the @react-pdf/renderer package (version 3.0.1) with a React 18 app, two problems arose. In this article, I'll describe those problems and tell you how I solved them.
Update: Here's a video demonstration of the problems and solution described in this article: https://youtu.be/YZP5r7Uy_bU
| { | |
| "PX1": "no_script", | |
| "PX2": "js_bootstrap", | |
| "PX3": "domready", | |
| "PX4": "fingerprint", | |
| "PX6": "nav_timing", | |
| "PX7": "incognito", | |
| "PX8": "score_session", | |
| "PX9": "score_impression", | |
| "PX10": "ui_interaction", |
| package transform | |
| import ( | |
| "reflect" | |
| "strings" | |
| "time" | |
| ) | |
| const ( | |
| tagName = "firestore" |
Normally, it is sufficient to grab the Go MSI installer from the website in order to set up the toolchain. However, some packages that provide Go wrappers for C libraries rely on cgo tool, which in turn, needs the GCC toolchain in order to build the glue code. Also, 3rd-party dependencies are usually hosted on services like GitHub, thus Git is also needed. This mini-guide illustrates how to setup a convenient development environment on Windows using MSYS2.
Notes:
Regarding the interception of HTTP:
We did it through USB reverse tunneling and iptable rules local to the phone.
As Gecko is moving toward more Rust code, the cases where Rust and C code interoperate will become more common.
This document is an attempt to ease the learning curve for engineers facing it for the first time. It assumes no prior experience with cross-language C interfaces (called FFI).
It also assumes that Rust code is already built into Gecko. If you need help with that, read Introducing Rust code in Firefox.
Note: This gist may be outdated, thanks to all contributors in comments.
adb is the Android CLI tool with which you can interact with your android device, from your PC
You must enable developer mode (tap 7 times on the build version in parameters) and install adb on your PC.
Don't hesitate to read comments, there is useful tips, thanks guys for this !
| sudo vim /etc/fstab | |
| # Comment out lines that have the word swap on them | |
| sudo reboot |
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
