Skip to content

Update docs: running a custom Node.js TiddlyWiki version with npx#9886

Open
vuktw wants to merge 1 commit into
TiddlyWiki:masterfrom
vuktw:vuktw-docs
Open

Update docs: running a custom Node.js TiddlyWiki version with npx#9886
vuktw wants to merge 1 commit into
TiddlyWiki:masterfrom
vuktw:vuktw-docs

Conversation

@vuktw

@vuktw vuktw commented Jun 21, 2026

Copy link
Copy Markdown

@netlify

netlify Bot commented Jun 21, 2026

Copy link
Copy Markdown

Deploy Preview for tiddlywiki-previews ready!

Name Link
🔨 Latest commit 6088e6f
🔍 Latest deploy log https://app.netlify.com/projects/tiddlywiki-previews/deploys/6a38584ad7bc6c00082b436f
😎 Deploy Preview https://deploy-preview-9886--tiddlywiki-previews.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

To edit notification comments on pull requests, go to your Netlify project configuration.

@github-actions

Copy link
Copy Markdown

@vuktw It appears that this is your first contribution to the project, welcome.

With apologies for the bureaucracy, please could you prepare a separate PR to the 'tiddlywiki-com' branch with your signature for the Contributor License Agreement (see contributing.md).

@github-actions

github-actions Bot commented Jun 21, 2026

Copy link
Copy Markdown

⚠️ Warning: This PR only modifies documentation (within /editions or /community/people). If the changes do not relate to the prerelease, please consider targeting the tiddlywiki-com branch instead.


✅ Change Note Status

This PR contains documentation or configuration changes that typically don't require a change note.

@vuktw vuktw changed the title Update docs: running a custom Node.js TiddlyWiki version with npc Update docs: running a custom Node.js TiddlyWiki version with npx Jun 21, 2026
@pmario

pmario commented Jun 22, 2026

Copy link
Copy Markdown
Member

I personally am not so happy to execute untrusted code directly from the internet. I consider a security hazard. -- I am not sure if we should promote it.

I personally vote. No

@Jermolene

Copy link
Copy Markdown
Member

Thanks @vuktw. @pmario makes some good points but given that this is a docs change I think it would be reasonable to just add caveats in the docs that reflect the concerns that @pmario has raised.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants