0.7.7 broken

[Martin Aspeli]

Hi,

Release 0.7.7 seems to not work when running "buster-test" because it is trying to load "buster-cli", which doesn't seem to exist anymore.

Also, it would be really great if there was a changelogs with each release. The one on the website is out of date. The technique I tend to use, is to just keep a list in README.txt and just add an entry each time I make a change.

Martin

[Christian Johansen]

Hi,

That sounds weird. buster-cli does still exist. Also, I used 0.7.7
successfully earlier today. Could you paste the error, or somehow be
more specific?

Christian

[Martin Aspeli]

Hi,

This was an upgrade from 0.6 by updating the dependency version in my package. However, i just tried blowing away node_modules and starting from scratch and it seems to work. Sorry about the noise.

Martin

—
Sent from Mailbox for iPhone

--
You received this message because you are subscribed to the Google Groups "Buster.JS" group.
To unsubscribe from this group and stop receiving emails from it, send an email to busterjs+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Christian Johansen]

No, sorry for breaking your tools :/ I've not had much luck with upgrades other than complete removal + reinstall in the past, so I guess that's the recommended route.

[Garrick Cheung]

Whenever I come across an issue where `npm install` or `npm upgrade` doesn't help, I uninstall, then `npm cache clean` to empty out npm cache so everything is downloaded anew.

[August Lilleaas]

Perhaps the "buster" and "buster-node" packages should start using
explicit dependencies instead of fuzzy semver matches, so updates work
better?

[Christian Johansen]

August Lilleaas writes:

> Perhaps the "buster" and "buster-node" packages should start using
> explicit dependencies instead of fuzzy semver matches, so updates work
> better?

That is not the root cause here. The problem was that I simply forgot
that the buster-module also depends on samsam, not only formatio.

This is the root cause:

formatio depends on samsam. However, in order to load samsam into the
browser when you type `buster-test`, the buster-module also depends on
samsam, so it can do `require.resolve("samsam")` (which wouldn't work
with node_modules/formatio/node_modules/samsam).

I want to fix this, and my current idea is to make all the buster
modules expose their own dependencies to help with loading them in the
browser. Example:

require("formatio").files; //=>
// ["node_modules/formatio/node_modules/samsam/lib/samsam.js",
// "node_modules/formatio/lib/formatio.js"]

This way we could remove the duplicated dependencies in the
buster-module, and this problem would go away.

Christian