this seems like it would be pretty useful for dendron preview and the 11ty template (or the next template thats under development right now) https://twitter.com/orta/status/1401868626953650176?s=21

neat! will look into this!

Is this the right place for this?

this is good. in the future, you could post it in #739186036495876126 as well 🙂

Oh my bad, will do

Hitting a build issue when running 'yarn bootstrap:build' $ yarn bootstrap:build: @Userhq/common-all $ npx lerna run build --scope @Userhq/common-all lerna notice cli v3.22.1 lerna notice filter including "@Userhq/common-all" lerna info filter [ '@Userhq/common-all' ] lerna info Executing command in 1 package: "yarn run build" lerna ERR! yarn run build exited 2 in '@Userhq/common-all' lerna ERR! yarn run build stdout: $ yarn clean && yarn format && yarn lint && echo Using TypeScript && tsc --version $ rimraf lib && rimraf coverage $ cd ../.. && yarn format:pkg $npm_package_repository_directory $ prettier --write $npm_package_repository_directory info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. lerna ERR! yarn run build stderr: warning package.json: License should be a valid SPDX license expression warning package.json: License should be a valid SPDX license expression warning package.json: License should be a valid SPDX license expression [error] No files matching the pattern were found: "$npm_package_repository_directory". @User , is it related to this change? https://github.com/dendronhq/dendron/commit/8ab97017ec377d11c0f448ab1e8aaa43c26d1159 Do I need to setup an environment variable?

yeah, just noticed this today too. new versions of npm removed the $npm_package_repository_directory variable

pull from the latest commit of

dev-kevin

that should have the fix

For anyone who's curious, here's how progress on filtering the new graph view is coming along

Having the filtered layout animating in rather than triggering full graph re-layout is v. slick 🙂

It was really satisfying to see in action - it's one of the benefits of using Cytoscape, as they have some pretty performant ways to manipulate and animate graphs

for interested parties, me and @User went through the dendron initialization process yesterday during a pairing session. notes in the dev branch of dendron-site: https://github.com/dendronhq/dendron-site/blob/dev/vault/pro.dendron-engine.arch.md#L11:L11 video here:

Hey in my spec file I am using "preSetupHook: ENGINE_HOOKS.setupBasic" . Although the test runs in local, in pipeline it gives error as: Module '"@Userhq/common-test-utils"' has no exported member 'ENGINE_HOOKS'.

Is anyone aware of such error?

we've refactored this to engine_test_utils

you'll want to run a

./bootstrap/scripts/cleanup.sh

to get rid of old files

Sorry @User for the VSCode question - on the dendron initialization video you show very interesting editor groups management - seem to show toggling between different sets of editor groups with different layouts. Could I trouble you to share your method, or simply point to any plug-ins that support this, when you have a chance? I've been using a small plugin Toggle Maximize Editor to expand one editor pane at a time when there are multiple splits open - but I can't see how to construct multiple layout of editor groups. Thanks!

that's actually me toggling between different windows of vscode 😅 i like to use different vscode windows for different contexts - see the writeup here: https://www.kevinslin.com/notes/7f197479-279e-4b1e-9edd-21bf2da423b0.html#dendron-setup

@User So good of you to share!

Does dendron-cli depend on the wrong version of dendron-11ty? Dependency resolution is failing and the latest published version is 1.45.2:

❯ npm ls @dendronhq/dendron-11ty
@lukecarrier/brain@0.1.0 /Users/lukecarrier/Code/LukeCarrier/brain
└─┬ @dendronhq/dendron-cli@0.45.1
  └── @dendronhq/dendron-11ty@0.45.1

hmm, the latest version of the cli should be 0.45.2. can you try upgrading?

The CLI version is 0.45.2, but I think it depends on the wrong version of dendron-11ty:

I think the the 11ty version constraint should be ^1.45.x?

ah, i see what you mean. yeah, 11ty versioning is confusing. it used to be published outside of the monorepo and started with 1.x version whereas the monorepo started with 0.x after we synced, we synced 11ty versioning and brought it down to 0.x. every minor release, we also publish the 1.x version of the 11ty package to make it consistent but during patch releases, we just keep the 0.x numbering. its a bit of a hack and something that should go away in a month when we introduce the nextjs based publishing

With no package-lock.json or node_modules dir and a package.json that depends on just dendron-cli@latest I can't install right now... I noticed this when my publishing action stopped working 😕

I'll take another look tomorrow, I don't think heat stroke from a beach day is helping my patience with npm 😂

got it. in that case, what we might do is switch to publishing the 1.x line every time we publish a minor version