Make the package publishable
See original GitHub issueAs a StarkNet smart contract developer, I want to import the protostar
package as a python dependency to use it in my tooling suite.
Issue Analytics
- State:
- Created a year ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Make existing library publishable · Issue #2329 · nrwl/nx · GitHub
I have a shared angular library in NX morepo workspace which is not publishable. I at least want it to be packageable (create...
Read more >Buildable and Publishable Libraries - Nx
To publish the library (for example to npm) you can run the CLI command: npm publish from the artifact located in the dist...
Read more >Creating and publishing scoped public packages - npm Docs
By default, scoped packages are published with private visibility. To publish a scoped package with public visibility, use npm publish --access public ....
Read more >How to Publish an Open-Source Python Package to PyPI
In this step-by-step tutorial, you'll learn how to create a Python package for your project and how to publish it to PyPI, the...
Read more >Publishable libraries with Nx Monorepo - part 1
inside every new generated library you have its package.json and its README. You need to update it by yourself and after building you'll...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You can rename
src
directory in your project for the time being.TBH, I don’t want to merge your PR yet because it will cause a lot of conflicts right now. I think I’ll do it once after we remove
development
branch.I tried this but there are conflicts of namespace since “src” was used as a root folder for all the source files. Actually my PR only renames this root folder to a
protostar
folder, in case we merge this one you are right that a submodule would work for us, without having to publish the package.