| pi@ratos:/dev/dri $ ls -al │ | |
| total 0 │ | |
| drwxr-xr-x 3 root root 120 Aug 27 14:34 . │ | |
| drwxr-xr-x 16 root root 3960 Aug 27 14:34 .. │ | |
| drwxr-xr-x 2 root root 100 Aug 27 14:34 by-path │ | |
| crw-rw---- 1 root video 226, 0 Aug 27 14:34 card0 |
These snippets are thanks and credit to taras.one/blog/dynamic-micro-frontends-with-nx-and-react
This is a workaround (an added feature really) for the nx react dynamic module federation capability not yet being present in nx. Instructions for use in blog post above.
| #!/bin/sh | |
| # Amend the commit message one specific commit and rebase | |
| # to apply the changes. Given the SHA hash or a reference | |
| # of the commit to amend, it checkouts the commit, amends | |
| # it interactively and rebases the repo history in current branch. | |
| # | |
| currentbranch=$(git branch --show-current) |
| // create context with no upfront defaultValue | |
| // without having to do undefined check all the time | |
| function createCtx<A>() { | |
| const ctx = React.createContext<A | undefined>(undefined) | |
| function useCtx() { | |
| const c = React.useContext(ctx) | |
| if (!c) throw new Error("useCtx must be inside a Provider with a value") | |
| return c | |
| } | |
| return [useCtx, ctx.Provider] as const |
| (MSG, Attach Probe) | |
| M0 | |
| G38.2 Z-50 F60 | |
| G90 | |
| G10 L20 P1 Z0 | |
| G91 | |
| G0 Z15 | |
| G90 | |
| (MSG, Detach Probe) | |
| M0 |
| import { | |
| ApolloClient, | |
| HttpLink, | |
| InMemoryCache, | |
| } from '@apollo/client' | |
| export const Client = new ApolloClient({ | |
| cache: new InMemoryCache(), | |
| link: new HttpLink({ | |
| uri: 'http://localhost:4000/graphql' |
Note: currently only works on *nix systems (until a powershell script can be created)
With the technique below, you can run node, npm, npx, or yarn commands as if the programs were installed
natively on your system, and you won't even know the difference! This includes any ports that your app or dev process
will start up and use for development, as well as compatibility with persistent npm config --global cli usage.
See more in the Usage section below.
I got the E3D Hemera (formerly called the Hermes) a week ago, and at first glance was impressed by the amount of documentation/guides E3D worked with popular YouTubers to create.
However, as time went on with my install, I discovered each guide was missing critical information, had bits of information incorrect, or included firmware files in a old or flattened format, making it difficult to discern firmware changes required.
I'm very familiar with Marlin 2.x, and so I finally decided to just go straight to the Hemera Datasheet, and finally got things working.
I'm not going to do a full guide, since I'm hoping one of the popular YouTubers who is capable of a high production quality video will do a comprehensive guide, but I have put together the following tips and lessons learned that should help some of you who are struggling but can't figure out why things aren't working.
*For reference: I have an Ender 3 with an SKR 1.3 using Marlin 2.x, equipped with TMC
| /** | |
| * Marlin 3D Printer Firmware | |
| * Copyright (C) 2019 MarlinFirmware [https://github.com/MarlinFirmware/Marlin] | |
| * | |
| * Based on Sprinter and grbl. | |
| * Copyright (C) 2011 Camiel Gubbels / Erik van der Zalm | |
| * | |
| * This program is free software: you can redistribute it and/or modify | |
| * it under the terms of the GNU General Public License as published by | |
| * the Free Software Foundation, either version 3 of the License, or |
| # Hello, and welcome to makefile basics. | |
| # | |
| # You will learn why `make` is so great, and why, despite its "weird" syntax, | |
| # it is actually a highly expressive, efficient, and powerful way to build | |
| # programs. | |
| # | |
| # Once you're done here, go to | |
| # http://www.gnu.org/software/make/manual/make.html | |
| # to learn SOOOO much more. |