This article address some common problems/caveats when using WSL as your daily development environment.
“Chrome Direct Print” is abandoned in favor of “WebApp Hardware Bridge“
Which support all modern browsers (Chrome, Firefox, Edge),
with better compatibility, performance and serial port support.
The most challenging (and missing) part of Web-based applications (especially internal systems) is printing.
Browsers do not allow silent printing and users demand it heavily.
“Chrome Direct Print” bridge the gap between Printer and Web Apps.
** Support Windows, Chrome and PDF only **
“Chrome Direct Print” make use of “Native Messaging API” to communicate with processes (aka host).
The “host” is written in Python, which is responsible for enumerating printers,
download PDF documents, and finally calling embed PDF reader to send PDF to printer.
This project is no longer maintained.
Source code here are for reference and study purpose only.
Chrome Extension: https://github.com/imTigger/chrome-hardware-bridge-app
NSIS Installer: https://github.com/imTigger/chrome-hardware-bridge-installer
This article requires Windows 10 (Build Version 1709 [The Fall Creators Update]) or above to work.
Although WSL exists since Version 1607 [Anniversary Update], it’s harder to setup and more buggy.
In this tutorial we will setup this development environment in WSL (In Part 1)
PHP 7.2 (Run as FPM)
With those tools under Windows 10 (In Part 2)
Bash and Linux CLI tools