question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docs navigation broken on mobile

See original GitHub issue

Shrink your browser down to < 600px so you see the mobile optimized page (single column) and click on any of the navigation. You’ll get an error like this in the console:

screen shot 2018-04-02 at 3 02 33 pm

I tracked down the error, and it looks like we may not be using the proper NODE_ENV when we build the website in production.

screen shot 2018-04-02 at 3 06 31 pm

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
pshrmncommented, Apr 3, 2018

@sag1v you have to run npm run build in the root so that the monorepo packages get built. I updated the CONTRIBUTING.md file earlier to reflect this, but as I mentioned in #6061, we should probably auto-build after install so that new contributors don’t have to go looking for build instructions.

0reactions
mjacksoncommented, Apr 24, 2018

I created an un-minified webpack build to try and figure out what is going on here (see attached) 🕵️

It looks like our bundle includes a process shim which is preventing process.env.NODE_ENV from being evaluated properly at build time, so the debugging code with the _debugID isn’t being stripped out.

screen shot 2018-04-24 at 9 25 36 am

However, it also looks like we have a bundle within our bundle, probably because the Animated code isn’t an actual dependency (it’s just copied over from an older version of the library) 🙃

For example, you can see here that entry # 463 in the outer bundle actually exports a webpack bundle of the Animated library:

screen shot 2018-04-24 at 9 28 06 am

So I’m guessing we need to either a) fix that inner bundle and get the process shim out of it so the webpack DefinePlugin can do its job and replace all the process.env.NODE_ENV references or b) figure out which commit (git bisect, anyone?) caused this weird behavior and undo the regression.

I’ve uploaded my build here in case anyone would like to go poking around

👇 build.zip

Read more comments on GitHub >

github_iconTop Results From Across the Web

Docs navigation broken on mobile · Issue #6058 - GitHub
I'm not sure what was the reason for using react-css-property-operations but it seems that it is abandoned and probably is not supporting react ......
Read more >
How to fix Maps when it crashes - Android - Google Maps Help
If the Google Maps app on your phone or tablet crashes or has other issues that affect your experience on Maps, try the...
Read more >
Get started with the Navigation component - Android Developers
In the Navigation Editor, click the New Destination icon , and then click Create new destination. · In the New Android Component dialog...
Read more >
Petal Maps – GPS & Navigation - Apps on Google Play
Petal Maps is a unique map that lets you explore the world around you in new ways. Available in over 160 countries and...
Read more >
Add Fixed Navigation on Mobile | Themeco Docs
A fixed navigation on mobile can be achieved by adding custom css to the theme. You can do so by going to: X/Pro...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found