Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

document d2js #261

Open
alixander opened this issue Feb 26, 2025 · 2 comments
Open

document d2js #261

alixander opened this issue Feb 26, 2025 · 2 comments

Comments

@alixander
Copy link
Contributor

No description provided.

@MichaelCropper
Copy link

Commenting to follow updates.....

@MichaelCropper
Copy link

Something isn't quite aligned here re. CI/CD for D2JS and the recent @nightly Build specifically.

I've encountered non-@nightly versions getting @nightly releases, which is incorrect from a Consumer perspective.

i.e.

import { D2 } from 'https://esm.sh/@terrastruct/d2';

VS

import { D2 } from 'https://esm.sh/@terrastruct/d2@nightly';

Producing the same result, which I wouldn't expect.

Perhaps I'm missing something related to the Release Version / Tagged Version (Current 0.6.9), given than D2JS is only a PART of the Release, I assume.

I can't quite second guess the setup.

Hopefully the As-Is Documentation can help explain this nuance, and help the community provide thoughts on a To-Be SDLC re. the D2JS specifically.

Also the D2 Playground seems to be ahead of D2JS, which I can only assume is down to the underlying architecture - again, hopefully this will be explained off the back of this discussion. I can only assume that the D2 Playground has a decoupled Front End / Back End to power it.

Thankfully this is a self-fulfilling prophecy due to the tooling we have at our fingertips 👍

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

No branches or pull requests

2 participants