add package.json to static .well-known by default #405
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ryanatkn
commented
Sep 24, 2023
| @@ -0,0 +1,5 @@ | |||
| --- | |||
greatbacon
reviewed
Sep 27, 2023
| The `gro exports` task, which is called during the dev and build tasks, | ||
| performs two separate steps that both call `package_json` to determine their behavior: | ||
|
|
||
| - when `when === 'updating_exports'`, Gro is updating the repo's `package.json` `"exports"` property |
There was a problem hiding this comment.
Sorry, I'm being lazy and not opening a fork, but might I suggest:
"with `when...." just to avoid the double when.
There was a problem hiding this comment.
good note thank you, did that and some other clarifications here - 8a257a9
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds new default behavior. The
package.jsonis included in the static directory duringvite build(non-destructively), so it gets deployed as${base}/.well-known/package.json. The docs include more details.It's nonstandard, couldn't find prior art, but I'm going to use the functionality it provides starting with
@fuz.dev/fuz-docs. With Webfinger being used by ActivityPub/Fediverse and Node being the target for Deno and Bun, this seems like the obvious choice. See Wikipedia - https://en.wikipedia.org/wiki/Well-known_URIsThe usecase for the fuz-docs is to be able to populate that project with data via a list of
hosts. I want the source of truth for fuz-docs to be the git repo contents of each individual project that it references, and have fuz-docs just be built and deployed to the static website on demand. The goal is to have the config be as simple as possible, just a list ofhosts to begin with.This would make a good API for users, too, because
hosts are easy to define and move around, and anyone could mix and match libraries and publish their docs/etc.I'm sure some of this will change, I'm just trying to enable some usecases for data/module sharing across many projects using HTTP and not git.