mkdnflow.nvim VS TypeScript

I like logseq for knowledge management and tasks. And since it's all plain markdown files they are easy to quickly open and search in nvim. https://github.com/jakewvincent/mkdnflow.nvim is really nice for this because it can follow the internal links and create new pages.

I've been planning to switch to https://github.com/jakewvincent/mkdnflow.nvim and re-write the function that creates diary pages, and the functions that cycle/navigate to next/prev diary pages, so that they work in subdirs... for example: main wiki is ~/diary and the main diary is in the root of that wiki and I want to be able to flexibly create dated files in any subdir without making that its own wiki so like in ~/diary/subdirxyz/2023-03-17.mkd the nextDay() function (whatever it's called) would look for next dated file only inside subdirxyz.

There are some cool features we've talked about adding to mkdnflow.nvim!!!

https://github.com/jakewvincent/mkdnflow.nvim is a similar plugin to neorg that's closer to vimwiki than to org-mode. Either way, a personal documentation system, and whatever report/scripts/grep to find things easily.

Did you see https://github.com/jakewvincent/mkdnflow.nvim/ mentioned here? I think that's the winner here (though I admit I have bias against even considering zettlekesten/zk merely due to its name: in computing we call that a wiki).

My markdown plugin mkdnflow does this (among other things). If you’re not looking for any functionality except toggling checkboxes, you could take a look at the lists module lists.lua and search for the function toggleToDo() (and those it relies on).

I'm using zk-nvim with markdown lsp, markdown / markdown_inline Treesitter and MKDNFLOW for my notes and tasks. This all works great and I also created this shortcut to archive selected lines to a different file

I use mkdnflow.nvim for taking notes in markdown. It is simple, and you can easily create and follow links.

I use markdown for all of my notes inside of Neovim and have a few custom macros and shortcuts, and heavily use iamcco's [MarkdownPreview](https://github.com/iamcco/markdown-preview.nvim) along with jakewvincent's [MkdnFlow](https://github.com/jakewvincent/mkdnflow.nvim).

Not sure what exactly you mean by editing lists and tables with ease, but my plugin https://github.com/jakewvincent/mkdnflow.nvim might check some of those boxes. What list and table editing features would be must-haves for you?

While we were fighting against the modules, we forgot one small detail - their built-in typings. Esbuild can't do this at all yet. Unbelievable, but the tsc, native TS compiler, also does not provide a typings concat feature. Got around this problem: we've introduced [a utility to combine typings](tsc-dts-fix of zx own code, and applied some monkey patches for external libdefs squashed via dts-bundle-generator.

Regular expressions are part of the language, so it's not so unreasonable that TypeScript should parse them and take their semantics into account. Indeed, TypeScript 5.5 will include [new support for syntax checking of regular expressions](https://github.com/microsoft/TypeScript/pull/55600), and presumably they'll eventually be able to solve the problem the GP highlighted on top of those foundations.

Dedicated syntax for creating unique subsets of a type that denote a particular refinement is a longstanding ask[2] - and very useful, we've experimented with implementations.[3]

I don't think it has any relation to runtime type checking at all. It's refinement types, [4] or newtypes[5] depending on the details and how you shape it.

[1] https://github.com/microsoft/TypeScript/blob/main/src/compil...

GitHub | Website

Learning Curve and Developer Tooling sCrypt is an embedded Domain Specific Language (eDSL) based on TypeScript. It is strictly a subset of TypeScript, so all sCrypt code is valid TypeScript. TypeScript is chosen as the host language because it provides an easy, familiar language (JavaScript), but with type safety. There’s an abundance of learning materials available for TypeScript and thus sCrypt, including online tutorials, courses, documentation, and community support. This makes it relatively easy for beginners to start learning. It also has a vast ecosystem with numerous libraries and frameworks (e.g., React, Angular, Vue) that can simplify development and integration with Web2 applications.

As a JavaScript or TypeScript developer, you might have come across the terms type and interface when working with complex data structures or defining custom types. While both serve similar purposes, they have distinct characteristics that influence when to use them. In this blog post, we'll delve into the differences between types and interfaces in TypeScript, providing examples to aid your understanding.

TypeScript helps you in many ways in the context of a JavaScript app. It makes it easier to consume interfaces of any type.

In this guide, we'll be extracting information from Amazon product pages using the power of TypeScript in combination with the Cheerio and Crawlee libraries. We'll explore how to retrieve and extract detailed product data such as titles, prices, image URLs, and more from Amazon's vast marketplace. We'll also discuss handling potential blocking issues that may arise during the scraping process.

TypeScript