New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unknown package error, while package clearly exists.... #7721

Closed
sebakerckhof opened this Issue Aug 27, 2016 · 15 comments

Comments

Projects
None yet
@sebakerckhof
Contributor

sebakerckhof commented Aug 27, 2016

Often when adding a package to the 'use' list of another package, I get an error that the package does not exist, while I'm sure it does.

E.g.:

C:\Users\seba\AppData\Local\.meteor\packages\meteor-tool\1.4.1_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:165
      throw error;
      ^

Error: Depending on unknown package pbastowski:angular-babel
    at Error (native)
    at processUse (C:\tools\isobuild\package-source.js:1707:15)
    at Array.forEach (native)
    at Function._.each._.forEach (C:\Users\seba\AppData\Local\.meteor\packages\meteor-tool\1.4.1_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\underscore\underscore.js:79:11)
    at C:\tools\isobuild\package-source.js:1717:9
    at Array.forEach (native)
    at Function._.each._.forEach (C:\Users\seba\AppData\Local\.meteor\packages\meteor-tool\1.4.1_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\underscore\underscore.js:79:11)
    at PackageSource.getPackagesToLoadFirst (C:\tools\isobuild\package-source.js:1712:7)
    at IsopackCache._ensurePackageLoaded (C:\tools\isobuild\isopack-cache.js:238:39)
    at C:\tools\isobuild\isopack-cache.js:76:14
    at C:\tools\packaging\package-map.js:57:7
    at Function._.each._.forEach (C:\Users\seba\AppData\Local\.meteor\packages\meteor-tool\1.4.1_1\mt-os.windows.x86_32\dev_bundle\lib\node_modules\underscore\underscore.js:87:22)
    at [object Object].eachPackage (C:\tools\packaging\package-map.js:49:7)
    at IsopackCache.buildLocalPackages (C:\tools\isobuild\isopack-cache.js:75:24)
    at C:\tools\project-context.js:781:25
    at C:\tools\utils\buildmessage.js:359:18
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:352:34
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:350:23
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
    at ProjectContext._buildLocalPackages (C:\tools\project-context.js:780:18)
    at C:\tools\project-context.js:268:9
    at C:\tools\utils\buildmessage.js:359:18
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:352:34
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:350:23
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at Object.enterJob (C:\tools\utils\buildmessage.js:324:26)
    at ProjectContext._completeStagesThrough (C:\tools\project-context.js:258:18)
    at C:\tools\project-context.js:250:12
    at Function.run (C:\tools\tool-env\profile.js:489:12)
    at ProjectContext.prepareProjectForBuild (C:\tools\project-context.js:249:13)
    at C:\tools\runners\run-app.js:548:29
    at C:\tools\utils\buildmessage.js:271:13
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:264:29
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:262:18
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at C:\tools\utils\buildmessage.js:253:23
    at [object Object].withValue (C:\tools\utils\fiber-helpers.js:89:14)
    at Object.capture (C:\tools\utils\buildmessage.js:252:19)
    at bundleApp (C:\tools\runners\run-app.js:547:31)
    at AppRunner._runOnce (C:\tools\runners\run-app.js:625:35)
    at AppRunner._fiber (C:\tools\runners\run-app.js:884:28)
    at C:\tools\runners\run-app.js:402:12

Stopping and restarting meteor gives the same error. Only when executing a meteor reset, the problem is gone and the package is added.

Reproduction
If you checkout this repo:
https://github.com/sebakerckhof/meteor-7721

Start the app, and while it's running, uncomment this line:
https://github.com/sebakerckhof/meteor-7721/blob/master/packages/foo/package.js#L12
you should get the error.

@laosb

This comment has been minimized.

Show comment
Hide comment
@laosb

laosb Aug 27, 2016

Collaborator

That's might be related to cache?

Collaborator

laosb commented Aug 27, 2016

That's might be related to cache?

@laosb

This comment has been minimized.

Show comment
Hide comment
@laosb

laosb Aug 27, 2016

Collaborator

Can you provide a reproduction? That might be hard, but without it we can't do much on it.

Collaborator

laosb commented Aug 27, 2016

Can you provide a reproduction? That might be hard, but without it we can't do much on it.

@cesarve77

This comment has been minimized.

Show comment
Hide comment
@cesarve77

cesarve77 Aug 27, 2016

Same issue

for reproduction
Just remove meteor
sudo rm /usr/local/bin/meteor
rm -rf ~/.meteor

instal meteor
curl https://install.meteor.com/ | sh

meteor create --package user:test

in /package/test/package.js insert
api.use(['aldeed:autoform'])

run meteor

and you will get

Error: Depending on unknown package aldeed:autoform

but if you install the package direct into app

meteor add aldeed:autoform

compile again, it works
maybe some with cache?

sorry for me inglish

cesarve77 commented Aug 27, 2016

Same issue

for reproduction
Just remove meteor
sudo rm /usr/local/bin/meteor
rm -rf ~/.meteor

instal meteor
curl https://install.meteor.com/ | sh

meteor create --package user:test

in /package/test/package.js insert
api.use(['aldeed:autoform'])

run meteor

and you will get

Error: Depending on unknown package aldeed:autoform

but if you install the package direct into app

meteor add aldeed:autoform

compile again, it works
maybe some with cache?

sorry for me inglish

@laosb

This comment has been minimized.

Show comment
Hide comment
@laosb

laosb Aug 27, 2016

Collaborator

Ah, that's must be something with cache.

Collaborator

laosb commented Aug 27, 2016

Ah, that's must be something with cache.

@queso

This comment has been minimized.

Show comment
Hide comment
@queso

queso Sep 2, 2016

Contributor

Getting the same issue here on 1.4.0.1

Contributor

queso commented Sep 2, 2016

Getting the same issue here on 1.4.0.1

@cesarve77

This comment has been minimized.

Show comment
Hide comment
@cesarve77

cesarve77 Sep 2, 2016

I solved updating meteor all packages and try again

El sept. 2, 2016 10:28 AM, "Josh Owens" notifications@github.com escribió:

Getting the same issue here on 1.4.0.1


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#7721 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADyXp_vfm7EZjWo4fiqhu4ocZ4b3l-aFks5qmDl4gaJpZM4JuqKN
.

cesarve77 commented Sep 2, 2016

I solved updating meteor all packages and try again

El sept. 2, 2016 10:28 AM, "Josh Owens" notifications@github.com escribió:

Getting the same issue here on 1.4.0.1


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#7721 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADyXp_vfm7EZjWo4fiqhu4ocZ4b3l-aFks5qmDl4gaJpZM4JuqKN
.

@abernix abernix added Impact:few and removed Impact:some labels Sep 14, 2016

@raphaelarias

This comment has been minimized.

Show comment
Hide comment
@raphaelarias

raphaelarias Sep 16, 2016

Same issue here. meteor reset resolves.

raphaelarias commented Sep 16, 2016

Same issue here. meteor reset resolves.

@peterchoo

This comment has been minimized.

Show comment
Hide comment
@peterchoo

peterchoo Dec 2, 2016

Contributor

If you're in a situation like me where you are working on an application where you cannot update meteor, you can delete meteor/local/resolver-result-cache.json - this forces Meteor to re-cache the packages available.

Contributor

peterchoo commented Dec 2, 2016

If you're in a situation like me where you are working on an application where you cannot update meteor, you can delete meteor/local/resolver-result-cache.json - this forces Meteor to re-cache the packages available.

@cpury

This comment has been minimized.

Show comment
Hide comment
@cpury

cpury Mar 10, 2017

This is still happening to me every time I add a new package and it's very annoying. If I was new to Meteor, this would frustrate me a lot. Can't we add a fallback to when a package is not found in the cache, it checks once more if the package is actually present or not?

cpury commented Mar 10, 2017

This is still happening to me every time I add a new package and it's very annoying. If I was new to Meteor, this would frustrate me a lot. Can't we add a fallback to when a package is not found in the cache, it checks once more if the package is actually present or not?

@chrisbutler

This comment has been minimized.

Show comment
Hide comment
@chrisbutler

chrisbutler Jun 26, 2017

seems like this has been an issue for a while, any ETA on a fix?

chrisbutler commented Jun 26, 2017

seems like this has been an issue for a while, any ETA on a fix?

@rubenpa

This comment has been minimized.

Show comment
Hide comment
@rubenpa

rubenpa Jun 26, 2017

Running meteor update my:package works for me, but this would be a very convenient fix.

rubenpa commented Jun 26, 2017

Running meteor update my:package works for me, but this would be a very convenient fix.

@hwillson

This comment has been minimized.

Show comment
Hide comment
@hwillson

hwillson Sep 13, 2017

Member

If anyone is still encountering this problem with a recent version of Meteor (>= 1.5.2), please provide a reproduction recipe to help with troubleshooting (see Reporting a bug in Meteor). Without reliable reproduction steps, there isn't much to go on here. I'll close this for now, but I'm happy to re-open this issue if anyone is still seeing this happen, and can provide a repro. Thanks!

Member

hwillson commented Sep 13, 2017

If anyone is still encountering this problem with a recent version of Meteor (>= 1.5.2), please provide a reproduction recipe to help with troubleshooting (see Reporting a bug in Meteor). Without reliable reproduction steps, there isn't much to go on here. I'll close this for now, but I'm happy to re-open this issue if anyone is still seeing this happen, and can provide a repro. Thanks!

@hwillson hwillson closed this Sep 13, 2017

@sebakerckhof

This comment has been minimized.

Show comment
Hide comment
@sebakerckhof

sebakerckhof Sep 14, 2017

Contributor

@hwillson this still exists in meteor >= 1.5.2 and can easily be reproduced.
If you checkout this repo:
https://github.com/sebakerckhof/meteor-7721

Start the app, and while it's running, uncomment this line:
https://github.com/sebakerckhof/meteor-7721/blob/master/packages/foo/package.js#L12
you should get the error.

Contributor

sebakerckhof commented Sep 14, 2017

@hwillson this still exists in meteor >= 1.5.2 and can easily be reproduced.
If you checkout this repo:
https://github.com/sebakerckhof/meteor-7721

Start the app, and while it's running, uncomment this line:
https://github.com/sebakerckhof/meteor-7721/blob/master/packages/foo/package.js#L12
you should get the error.

@hwillson

This comment has been minimized.

Show comment
Hide comment
@hwillson

hwillson Sep 14, 2017

Member

Thanks for the repro @sebakerckhof - re-opening.

Member

hwillson commented Sep 14, 2017

Thanks for the repro @sebakerckhof - re-opening.

@hwillson

This comment has been minimized.

Show comment
Hide comment
@hwillson

hwillson Mar 5, 2018

Member

While we think resolving this issue would be a great addition to the Meteor project, we're going to close it for now due to inactivity (see the bug issue lifespan section of Meteor's traige doc for more information). If anyone comes across this issue in the future, and is interested in working on resolving it, please let us know by posting here and we'll consider re-opening this issue. Thanks!

Member

hwillson commented Mar 5, 2018

While we think resolving this issue would be a great addition to the Meteor project, we're going to close it for now due to inactivity (see the bug issue lifespan section of Meteor's traige doc for more information). If anyone comes across this issue in the future, and is interested in working on resolving it, please let us know by posting here and we'll consider re-opening this issue. Thanks!

@hwillson hwillson closed this Mar 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment