Error in observer.next ... about vulcan-docs HOT 13 CLOSED

Any error on the server?

from vulcan-docs.

no, no errors from the server. Just a warning about BCrypt:
Note: you are using a pure-JavaScript implementation of bcrypt.

which I think is not related

from vulcan-docs.

What's http://localhost:3000/packages/my-package.js by the way? Why would you have a file there?

from vulcan-docs.

I don't now, it's automatically created by Meteor. It contains all the code I have write in the files as the tutorial describe, and it's in:

./.meteor/local/build/programs/server/packages/my-package.js
and
./.meteor/local/build/programs/web.browser/packages/my-package.js

And those two files are different

from vulcan-docs.

Oh ok if it's in there that's fine then, sorry. Let's try something else then, can you paste in your .meteor/versions file? You might have some outdated packages?

from vulcan-docs.

here:

[email protected]
[email protected]
aldeed:[email protected]
aldeed:[email protected]
aldeed:[email protected]
aldeed:[email protected]
aldeed:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]_1
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
fortawesome:[email protected]
fourseven:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
jparker:[email protected]
jparker:[email protected]
jparker:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
mdg:[email protected]
[email protected]
[email protected]
meteorhacks:[email protected]
meteorhacks:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
nova:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
percolatestudio:[email protected]
[email protected]
raix:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
softwarerero:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
std:[email protected]
tmeasday:[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]

Merci pour ton aide :)

from vulcan-docs.

No that looks alright to me… What if you try the framework-demo package directly instead of following the tutorial, does that work any better?

from vulcan-docs.

In order to enable the framework-demo I have to re-add in the .meteor/packages the packages the tutorial ask to delete. And if I do so, I get an error: Error: There is already a collection named "movies".

So I have to change the name of the collection in packages/my-package/lib/modules/collection.js, and if I do so the demo works good.

So the problem is in the tutorial package... But I don't have idea where to find it

from vulcan-docs.

Maybe you can just go file by file and compare your package's code with framework-demo's code?

from vulcan-docs.

ok, i try. Thank you!

from vulcan-docs.

That's weird: after checking everything, I just copied framework-demo in my-package, and modified the name in my-package/package.js. But pointing to localhost:3000/movies I have the same error!

So the problem should not be in the files, but somewhere else in the framework.

Moreover, even if the framework-demo is commented, as I point to localhost:3000/ I see it appearing.

Is there a ghost within my framework?

from vulcan-docs.

maybe try meteor reset?

from vulcan-docs.

Tried, but nothing changes. Still the same error in 'localhost:3000/movies', and still the presence of framework-demo in localhost:3000...

I did not mentioned that I always have two warnings on the browser console:
"Warning: fragment with name UsersCurrent already exists.
and
Warning: React attempted to reuse markup in a container but the checksum was invalid ....

But that should not be part of the problem, since they are present in both the addresses

from vulcan-docs.