Skip to content
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.

Sign up for GitHub

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

Jump to bottom

3.3.1-alpha.5 npm behaviour differs #128

Open
soyarsauce opened this issue Nov 17, 2020 · 2 comments
Open

3.3.1-alpha.5 npm behaviour differs #128

soyarsauce opened this issue Nov 17, 2020 · 2 comments

Comments

@soyarsauce
Copy link
Contributor

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
Copy link
Contributor

What does "different results" mean here?

@soyarsauce
Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KeyboardSounds @soyarsauce