Comments (2)
@syrusakbary, I just played around with this and I'm not sure if I like the way packages get named.
For example, wasmer/wasmer-pack
is turned into wasmer_package__wasmer__wasmer_pack
on Python and @wasmer-package/wasmer__wasmer-pack
on JavaScript. Compare that with wasmer_pack
and @wasmer/wasmer-pack
under the existing naming scheme.
I know package names are just labels, but they feel kinda clunky and could be a pain for end users to import every time.
Instead of publishing to PyPI and NPM, what if we hosted our own alternate registries? Pip, NPM, and Cargo all support the concept of alternate registries, and that way we wouldn't need to worry about namespacing.
I guess it's a trade off, though. Hosting our own registry gives us lots of flexibility, but most registries require you to only have dependencies from the same registry, so it means people can't use WAPM packages if they want to publish to PyPI/NPM/Crates.io 😞
from wasmer-pack.
This can be solved easily by a new --package-name
flag provided to the wasmer-pack
cli.
Where the user of the CLI actually decides what's the package name.
Wasmer pack can choose the default and users can override it.
This also helps if in the future we don't include the package name metadata in the webc
from wasmer-pack.
Related Issues (20)
- Add tests which install generated the tarballs
- Update JavaScript templates to allow importing host functions
- Update Python templates to allow importing host functions
- Write the host imports tutorial
- Create a set of integration test helpers HOT 1
- Update the bindings generator on WAPM when a new version is published
- Bindings/Commands not compatible with the browser HOT 3
- Don't count wasm4 commands as WASI commands HOT 1
- Automatically add commands to JS/Python packages
- Generated JavaScript filenames need to use kebab-case everywhere
- Unable to add my WAI package through yarn HOT 3
- [Bug]: Unable to generate bindings for `katei/irb`
- [Bug]: Hello World tutorial fails to publish
- WASI Support HOT 1
- Importing host functions (and implementing them in Rust)
- [Bug]: AssertionError: "<package>.wasm" is not a valid WASI executable HOT 1
- Support for generating JVM package
- Support for generating Go package
- Add support for volumes
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wasmer-pack.