Skip to content

App js assets uniquely named and next to apps/*/Project/*.amxd  #12

Description

@codekiln
  • [[GitHub/aptrn]]'s original template was for [[c74/max/standalone]], where there are [[c74/max/Project]]s that can manage the paths unique to each application so as to include each generated [[c74/max/js]] item.
  • I could add each library to the [[c74/max/File Browser]] path manually, which could work, but I have to be careful that each generated js file is uniquely named.
  • That doesn't seem like a great approach for portability or getting a great [[Dev/Experience]].
  • Instead, if we utilize [[rollupjs]] and [[Typescript]] options so everything is compiled to a file that's adjacent to the [[c74/M4L/.amxd]] file that's uniquely named, then the downstream developer won't have to mess with modifying [[c74/M4L/max]]'s paths.
  • Acceptance Criteria

    • Compiled application assets are added to git
    • Compiled application js assets are not nested in folders
    • Compiled application js assets are uniquely named

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions