You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Default doc-kit generation should not use Node.js branding #986
We are a Node.js / OpenJS project, why change the branding?
Because fresh installations of doc-kit should not come with our branding. Since this is supposed to be used by anyone. Only Node.js's specific usages should come with Node branding. Otherwise we're in violation of the Foundation copyright.
changed the title [-]Default doc-kit generation should not use Node.js[/-][+]Default doc-kit generation should not use Node.js branding[/+]on Aug 3, 2026
Activity
bmuenzenmeyer commentedon Aug 3, 2026
@avivkeller @araujogui @AugustinMauroy this is a stretch goal before Render
ovflowd commentedon Aug 3, 2026
avivkeller commentedon Aug 3, 2026
We are a Node.js / OpenJS project, why change the branding?
ovflowd commentedon Aug 3, 2026
Because fresh installations of doc-kit should not come with our branding. Since this is supposed to be used by anyone. Only Node.js's specific usages should come with Node branding. Otherwise we're in violation of the Foundation copyright.
avivkeller commentedon Aug 3, 2026
Oh, I misunderstood this issue lol, on it
ovflowd commentedon Aug 3, 2026
🙈
ovflowd commentedon Aug 3, 2026
avivkeller commentedon Aug 3, 2026
That's the plan for the monorepo, e.g.
addon-verify, etc[-]Default doc-kit generation should not use Node.js[/-][+]Default doc-kit generation should not use Node.js branding[/+]bmuenzenmeyer commentedon Aug 3, 2026
yeah i missed an essential word there in my haste to record it 🙃
remoteConfigUrlshould be the default #1006 as a duplicate of this issue