Merge packages into a single package.
See original GitHub issueMany projects need functionality both from core
and music_rnn
/ music_vae
. For example, you may need to use the NoteSequence or ControlSignal libraries as well as the main model class.
Also, some projects may use both RNN and VAE.
Currently this doesnt seem possible as RNN and VAE are in separate bundles, both of which contain their own copy of core as well as Tensorflow.
Would it make sense to create a magenta-full.js
bundle to easily include everything?
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
can we merge Multiple Packages in to Single Package in D3FO?
Merged package – A package that is created by combining one package of each type. For example, one binary update package, one AOT...
Read more >[feature] Merge multiple packages contents into a single ...
I wan't to merge libA, libB, libC, etc. package folders into a single folder with a single include, lib, etc folder for all...
Read more >Combine library packages into single node package
For any project I would want to put all the packages above react , react-dom , react-router and react-route-dom into a single node...
Read more >Merge packages
Click the Package tab, and then click Merge Package. Click Add and, in the Open dialog box, select an .hlkx package that you...
Read more >Merging Two Packages
Merging packages is straightforward as well. The following two cases are examples of merging packages: One package absorbs another package at the renamed ......
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
Our current plan is to move all of our current packages into a single @magenta/music package, leaving room for future models that don’t work with NoteSequences.
@cghawthorne, we should probably restructure the directories, e.g., move music_vae.ts and music_rnn.ts into a models directory. data.ts should probably be renamed to converters.ts since we have other data libs.
This’ll also maker #29 easier, as a
Player
class (and other demo code) can be shared between RNN and VAE demos without having to package it up into the NPM modules.