Can't get started with codelab theme or any other theme
See original GitHub issueHello 😃
I’m following the codelab of starting with grow: https://grow.io/codelab/3/ I run the commands in order
grow init codelab ./my-codelab/
cd my-codelab/
grow install
grow run
After the server is running I get this screen:
Clicking traceback prints false
. Tried other themes, all have similar problems. Tried grow preprocess
, same result.
Testing environment:
- OSX Mohave
- grow v.0.8.16
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to bring the colab dark theme to Jupyter Notebook
First, you have to install Jupyter Themes: pip install jupyterthemes. Then, i think Colab uses the theme "onedork", so just set it using:...
Read more >Enable Dark Theme on Google Colab (colab ... - YouTube
Learn how to enable dark them on Google Colaboratory. Colab notebooks combine executable code and rich text in a single document, ...
Read more >Google Colab! Changing Themes - YouTube
To change the background within Google Colab, select "Tools" then "Settings". Under the "Site" tab the themes can be changed to "light", ...
Read more >Using Dark Theme in Google Colaboratory - Buomsoo Kim
2. Change your theme. Change the theme to “dark.” It will be set to “light” by default and you can always come back...
Read more >Colab links always show up by default · Issue #209 - GitHub
Google Colab buttons will show up by default if launch buttons are set to true. This is because colab has a default URL...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This is happening because we removed our sass preprocessor in an earlier version of grow, but we never updated the codelab with that change. I’ll work on updating the codelab code to use a preprocessor for compiling the sass.
I’ve updated the codelab to use the gulp preprocessor to generate the sass instead of using the older built-in preprocessor.
I had to temporarily disable the error page generation since it was causing issues with grow. I’ll try and get that back sometime soon, but it should build and run correctly now if you redo the codelab.