devtools-frontend VS miktex

You can paste that curl command into https://curlconverter.com/wget/ to turn it into a Wget command.

> The reason there isn't a "Copy as wget" option, I think, is the level of control that curl allows so the request can be tailored to exactly mimic the browser.

This is not true. You can read the code that generates the curl command and it's pretty straightforward:

https://github.com/ChromeDevTools/devtools-frontend/blob/c9a...

The arguments it uses are --url, --data-raw, -X/--request, -H/--header, --compressed and --insecure, all of which Wget has an analog of. I think the reason is that they don't care to do it and/or they don't want to make that dropdown menu 30 entries long.

The GitHub mirror of the Chrome DevTools repo has the node_modules folder here: https://github.com/ChromeDevTools/devtools-frontend/blob/mai...

But there is nuance (there always is...), the README file in node_modules is here: https://github.com/ChromeDevTools/devtools-frontend/blob/mai... - and it makes it clear the only NPM dependencies used by the build-system or infrastructure is meant to be checked-in. Other NPM packages should not.

----------

In conclusion: the linked blog-article is clickbait that misrepresents how the Chrome team manages their dependencies.

While you are correct about Google's monorepository, the author works on Chrome DevTools. That repository is open-source and standalone: https://github.com/ChromeDevTools/devtools-frontend

What's new in DevTools (Chrome 95).

2 known issues:

- DevTools doesn't display the viewport. I'm not sure if this is due to a change in the latest Chrome to which I just updated (~90) or because I broke my serving of it by updating it. A workaround will be serving a static snapshot of the devtools front-end rather than just (simply, as I'm doing right now) pulling it out of Chrome's RDP endpoint each time. This may take some time to do.

- DevTools doesn't seem to work on iOS (as I've tested it, Safari or Chrome).

- There are many more issues, and a lot, but not all, of them are edge cases but they'll be fixed eventually.

More bug reports, UI/UX tips and advice, and other feedback are very welcome! Unfortunately the whole app is not open source but some parts are open source, namely, the virtualized browser[0], and the devtools-front-end[1].

[0]: https://github.com/i5ik/ViewFinderJS

[1]: https://github.com/ChromeDevTools/devtools-frontend

Usually people recommend miktex for windows https://miktex.org/

Seems like something's wrong with your MikTeX installation. Here's an issue on GitHub where others have had similar issues and here's another one.

For two, you can resort to its analogue within the KOMA class/bundle. Depending on your locale, this may require some adjustments for the paper format (ISO A4 vs e.g., US letter), but this is quick click in general setup (in case you happen to use MiKTeX, one of the tabs asks you for the format typically used) and in the .tex preamble. Else, achemso works just fine, i.e. in the text you get the number-based references.

Or, does the flatpack attempt an installation of a large portion/all of TeXLive? (Aiming for a more granular approach, to fetch only the packages I really want [with optional, yet independent download of the documentation] was a major motivation to move to MikTeX (non-Docker) installation equally running from a a thumb drive, or in Linuxes. This was something in close to 100...200 MB in total as a starter package (already with its package manager), to which one can add/update/remove by like/dislike, need/no-need. And by the documentation, an installer for Fedora 37 equally is provided.).

texdoc comes with TeXLive only. With MiKTeX (which equally works well in Linux as in Windows, and from a thumb drive), you select the packages (or their documentation, or both) of interest for download. A double click opens the .pdf (screenshot).

does the compilation with pdfLaTeX work? Do you use an instance of MiKTeX recently updated? A note about the GUI used would complement a problem report. If you use e.g., TeXStudio, then you already have a preview of the compiled document to monitor the advance of your work. You still can setup the program to open an external pdfviewer (e.g., sumatra) for a subsequent detailed inspection, print to paper of the pdf, etc. later.

Because you mention Texniccenter I assume the operating system you use is Windows. Often, your TeX installation is either a ProTeXt DVD/iso (source of the soon retired project), or miktex. MiKTeX can install many of potentially missing usepackages during the first compilation if 1) the computer can connect with the servers of CTAN and 2) the user has permission to install programs on drive C:\. (In addition, MikTeX' package management offers you to list the packages installed/update them if you wish.) In case you do not possess the permissions to install a program, consider the portable installation, on an USB thumb drive -- very handy e.g., when passing the library's computer without installation privileges. MikTeX's installation comes with a light TeX editor, too -- not as many buttons to click as TeXniccscenter or TeXStudio, but cross platform.

With an export of your .lyx to .tex, which may be submitted to pandoc. The entry Demos showcases some examples from which you may infer the syntax, the entry Demos -> Try pandoc online offers an installation free test ground e.g., from latex to .docx or .odt (or others). The less complex the .tex file, the greater the chances this minimal version will work, so forget (for now) illustrations and bibliographic references. However, if you install pandoc (freely available, cross-platform) and read the documentation, you may access much more functionality (including insertion of images, use of a bibliography; generation of .pdf with pdfLaTeX [e.g., with MikTeX], etc.) There equally is a r/pandoc, too.

Give me some rope here, because you don't describe the installation available to you. I assume it is possible for you to collect and process the .md files locally. If so, a joint installation of miktex (for the part of e.g., rendering equations with pdfLaTeX), and pandoc for the conversion of file formats, e.g., markdown to .pdf, is handy.