use observablehq:stdlib instead of npm:@observablehq/stdlib #1670
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The goal here is to differentiate packages that are built-in to Framework from ones that are published and loaded from npm. This PR only makes this change for the standard library (
observablehq:stdlib
), but if other built-in modules are provided in the future, we could useobservablehq:
for that, too.Note that there are several other libraries such as
npm:@observablehq/dot
that we intend to publish to npm in the future, but for pragmatism are currently implemented as built-ins. We don’t want to switch these toobservablehq:
because the desired future state is for these libraries to be published to and imported from npm rather than being built-in.Also some libraries as
npm:@observablehq/xlsx
andnpm:@observablehq/zip
should be private built-ins as these are not intended to be published to npm nor imported directly; they are only intended to be used byFileAttachment
and are imported asobservablehq:stdlib/xlsx
andobservablehq:stdlib/zip
.Related #852.