Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm rebuild does not guarantee clean rebuild #542

Closed
mraleph opened this issue Jan 30, 2011 · 2 comments
Closed

npm rebuild does not guarantee clean rebuild #542

mraleph opened this issue Jan 30, 2011 · 2 comments
Labels
bug

Comments

@mraleph
Copy link

mraleph commented Jan 30, 2011

I've expected npm rebuild to do a clean rebuild of package but when I tried it with daemon package I've noticed that it does not. I had to uninstall and install package again to force clean rebuild.
@isaacs
Copy link
Contributor

isaacs commented Feb 12, 2011

Note added in 1cd691f

@isaacs
Copy link
Contributor

isaacs commented Feb 14, 2011

Closed by 5f0c267 On second thought, no.

There are several edge cases that one finds down that road.
Since the cached contents may have been discarded, this could
effectively become a 'reinstall' command. That'd be fine,
but I think for a sugar method like this, it takes things
just a bit too far.

reid pushed a commit to reid/npm that referenced this issue Jul 8, 2011
@isaacs
FIXME note for npm#542
1cd691f
reid pushed a commit to reid/npm that referenced this issue Jul 8, 2011
@isaacs
Closes npmGH-542 On second thought, no.
5f0c267 
There are several edge cases that one finds down that road.
Since the cached contents may have been discarded, this could
effectively become a 'reinstall' command.  That'd be fine,
but I think for a sugar method like this, it takes things
just a bit too far.
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@isaacs @mraleph