angular-cli VS Joplin

module.exports = async (util, rule, host, injector) => { let list = await util.changeList([ { type: 'copy', source: 'git', from: { url: 'https://github.com/angular/angular-cli.git', match: '/packages/schematics/angular/directive/files', output: '/packages/schematics/angular/directive/files', }, pathTemplate: '@angular-devkit', contentTemplate: '@angular-devkit', pathTemplateSuffix: '.template', templateContext: { name: 'hello', standalone: true, selector: 'hello', 'if-flat': (input) => '' }, to: './hello-directive' }, ]); await util.updateChangeList(list); };

Well, scream though I have, the Angular team desperately needs to Remove NodeJS Dependencies, as it has already fallen behind from all frameworks concerning deployment. I'm still waiting for the response on this... 🦗 🦗 🦗 🦗

PR: feat(@angular-devkit/build-angular): add define build option to application builder

The new ssr CommonEngine source code

Source: https://github.com/angular/angular-cli/issues/25134

I'm not sure how to solve this but here's something that looks similar to your issue - https://github.com/angular/angular-cli/issues/24373

Sass errors after migrating from Angular 13 to 15 / Node 14 to 18

Edit: Found it at Github https://github.com/angular/angular-cli/issues/25574. So it seems to be a problem

Remove Dependencies for NodeJs

Is it possible to teach llm to read issues and answer questions such as how do I get angular 17 to output to dist instead of dist/browser with you can't do this with angular. However, in your CI CD pipeline, you can do a mv or robocopy or bla bla bla depending on context?

https://github.com/angular/angular-cli/issues/26028

It would be very useful because there are so many edge cases that aren't covered in the docs but are probably available in some kind of WON'T FIX issues.

I've had great success with using Joplin for this, with Syncthing as a sync backend. Works well across OSes; I use it on Linux, macOS, Windows and Android.

https://joplinapp.org/

The tools to manipulate SQL aren't that bad, no.

But rather than having a self explanatory markdown & flat file, now I have to start learning about the schema & making specific tools (in my preferred language) for manipulating Joplin's schema.

Suddenly I'm digging through 20 different technic specs to decode what data is where, how it works, and what I can do to it. Want to edit history? This is the best help you'll get, pray it's adequately technical to expedite you to your purpose: https://github.com/laurent22/joplin/blob/dev/readme/dev/spec...

As I began with, I struggle to imagine anything that generates anywhere near as much user agency as flat files and markdown. Having boring common data & systems lets me apply portable skills I already have, rather than having to skill up in some particular product's own ecosystem.

Joplin is a good open source option too, feels more like the original Evernote in terms of UI/UX https://github.com/laurent22/joplin/

Joplin, an open source, extendable, Markdown-based hierarchical note-taking app: https://joplinapp.org/

It lets you choose a synchronization backend, offers applications for every major desktop and mobile OS (also has a terminal version). You can create notebooks and subnotebooks to organize your notes. You can also add tags for better search experience. I created notebooks for specific domains (work-related, home improvement, etc.) and also keep a "temp" for quick notes and W.I.P. snippets.

Its only con that it uses Electron on desktop which causes relatively slow start of the application.

done