3.3.1-alpha.5 npm behaviour differs
soyarsauce opened this issue · 2 comments
soyarsauce commented
Using the 3.3.1-alpha.5 tagged release on npm yields different results to using a yarn workspace checked out to 3.3.1-alpha.5
I've unpacked the npm tarball for 3.3.1-alpha.5 - it all looks alright, but there must be something that differs for this behaviour to present. Perhaps try again with a new tag, on new tip, and go from there?
KeyboardSounds commented
What does "different results" mean here?
soyarsauce commented
Sorry!
(read: some of the features/config do not behave as expected)
Basically things like the multiserverconfig, noindex/index routing behaviour, will act as if they aren't available