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

ref(wasm-pkg): Updates well known file to point to official wasi repo #96

Conversation

thomastaylor312
Copy link

Since WebAssembly/WASI#606 has been accepted, we should probably make sure the current defaults for bytecodealliance.org actually point at the official wasi packages available here

Since WebAssembly/WASI#606 has been accepted,
we should probably make sure the current defaults for bytecodealliance.org
actually point at the official wasi packages available [here](https://github.com/orgs/WebAssembly/packages)

Signed-off-by: Taylor Thomas <[email protected]>
@thomastaylor312
Copy link
Author

cc @lann

@ricochet
Copy link
Collaborator

cc @disquisitioner

@thomastaylor312
Copy link
Author

thomastaylor312 commented Jun 17, 2024

@lann I cc'd you because I wanted to make sure this lined up with what you were thinking. I know you had mentioned a mirror of packages in the BA last time we talked, but I wasn't sure if that was for real or not. I saw the wasm-pkg ones obviously, but thought that was just for testing. Trying to point at whatever we consider the canonical location here.

My purpose here is that any wasi:* packages should come from the official WASI repo when using defaults. Since "bytecodealliance.org" is the default in the packaging tooling, that is why I think it should point there. But I could be ignorant of other things people had planned

@thomastaylor312
Copy link
Author

I don't know how I missed this, but this was in bytecodealliance/wasm-pkg-tools#41:

This PR also adds "namespace fallback" config, replacing the hard-coded bytecodealliance.org with two hard-coded fallbacks for wasi: and ba:; these both currently point at bytecodealliance.org but I expect to switch wasi: to wasi.dev once we have that registry properly configured.

So I'll close this because I misread that entirely. This one will still point at the proper BA repos and the new wasi.dev stuff will point at official wasi

@thomastaylor312 thomastaylor312 deleted the ref/update_well_known branch June 17, 2024 21:21
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.

2 participants