Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Packages need a principled way to access their files (and their build contents) #2506
I know this isn't an explicit bug, but there is a strong need to give packages a better way to access files before and during the build process. Many packages, including several of mine, have broken across the 0.9 migration with no clean way to fix them. I'll give some examples here; please consider how we might support these use cases.
Note that we need to manually find the folder for the package (previously
On a similar note, the Meteor 0.9 build process should be better documented - how raw files are treated, how the built files are stored, and what gets sent to the package server - and how build plugins interact with this process. build-fetcher broke in the transition from 0.8.3 to 0.9, and packages using it (such as
This was referenced
Sep 3, 2014
I reopened and renamed #1193. I'm not sure what other specific things you're looking for, other than just generally having more flexibility in what build plugins are allowed to do. We're aware that our build system only has a limited number of extension points and plan to increase them over time as we see what things our users are forced to hack around :)
#2488 was a very specific one line bug that we fixed due to your helpful report.
I don't think #1193 is asking for the same thing; it is for clients to be able to load assets of a package. I'm asking, on the server, for the package to be able to access the files under itself.
I'm trying to point out what I'm trying to do that needs to be extensively hacked around. I was hoping that we'd be able to have a discussion about what the package control format can support in the future.