The npm flexjs package is a thing on its own which points to only released Apache artifacts. We are not publishing unreleased apache code anywhere.
Still not sure what the violation is. Thanks, Om On Tue, Sep 13, 2016 at 3:12 PM, Josh Tynjala <joshtynj...@gmail.com> wrote: > If that's the case, I guess we'll need to switch to using "npm pack" for > testing NPM builds in the future. It produces an archive that is the same > as what gets downloaded when a version is published to NPM's servers, but > you can use it to install locally. > > Running the following command in the same directory as package.json creates > a file like flexjs-0.7.0.tgz: > > npm pack > > Then you can use the regular npm install command to install it: > > npm install -g flexjs-0.7.0.tgz > > We'll have to figure out somewhere to upload this TGZ package for testing, > since the configuration of different computers might accidentally produce > different output. > > - Josh > > On Tue, Sep 13, 2016 at 2:52 PM, Justin Mclean <jus...@classsoftware.com> > wrote: > > > Hi, > > > > > I have pushed the new bits as a pre-release to npm. > > > > Just a word of caution here, by doing this you are probably not in line > > with ASF policy. I could point you to the usual links about release etc > but > > this discussion on the incubator list is recent and relevant. [1] > > > > Thanks, > > Justin > > > > 1. https://lists.apache.org/thread.html/e5c17f08f30aa924bdfd50d215b3f4 > > 68269dc9198411b069d035a891@%3Cgeneral.incubator.apache.org%3E >
