Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

When using gatsby develop with JS disabled, instruct the user that the HTML for pages are not rendered on the server #374

Closed
savolai opened this issue Aug 2, 2016 · 2 comments
Closed

When using gatsby develop with JS disabled, instruct the user that the HTML for pages are not rendered on the server #374

savolai opened this issue Aug 2, 2016 · 2 comments
Labels
help wanted Issue with a clear description that the community can help with.

Comments

@savolai
Copy link

savolai commented Aug 2, 2016

instruct users on how to get both static and dynamic site running

Re: gatsbyjs/gatsby-starter-documentation#10 (comment)
@KyleAMathews KyleAMathews changed the title using gatsby develop with JS is disabled, instruct the user that static sites are not generated with gatsby develop When using gatsby develop with JS disabled, instruct the user that static sites are not generated with gatsby develop Oct 12, 2016
@KyleAMathews KyleAMathews changed the title When using gatsby develop with JS disabled, instruct the user that static sites are not generated with gatsby develop When using gatsby develop with JS disabled, instruct the user that the HTML for pages are not rendered on the server Oct 12, 2016
@KyleAMathews
Copy link
Contributor

In other words, instead of not including anything for the body when rendering in the dev server, add a <noscript> element with a message saying something like "The Gatsby development server does not work without Javascript enabled. If you'd like to test how your site works without Javascript, first build the site 'gatsby build' and then serve the built site 'gatsby serve-build'"

@KyleAMathews KyleAMathews added help wanted Issue with a clear description that the community can help with. Hacktoberfest labels Oct 12, 2016
@nason
Copy link
Contributor

nason commented Nov 19, 2016

Hi @KyleAMathews, I'd like to take this on. just ran into this situation and thought I would open an issue, but its already here. I'll have a PR up shortly.

Btw, thank you for this excellent tool!

nason added a commit to nason/gatsby that referenced this issue Nov 19, 2016
@nason
Add a noscript tag for better DX in develop mode with JS disabled
a7b0d35 
Fixes gatsbyjs#374
nason added a commit to nason/gatsby that referenced this issue Nov 19, 2016
@nason
Add a noscript tag for better DX in develop mode with JS disabled
1a45b46 
Fixes gatsbyjs#374
@nason nason mentioned this issue Nov 19, 2016
Merged
ChristopherBiscardi pushed a commit to ChristopherBiscardi/gatsby that referenced this issue Jun 9, 2019
@redallen @ChristopherBiscardi
Allow webpack loaders for relative imports (gatsbyjs#374)
c544996 
* Allow webpack loaders for relative imports

* Clean loader path logic
ChristopherBiscardi pushed a commit to ChristopherBiscardi/gatsby that referenced this issue Jun 27, 2019
@redallen @ChristopherBiscardi
Allow webpack loaders for relative imports (gatsbyjs#374)
d7e4102 
* Allow webpack loaders for relative imports

* Clean loader path logic
johno pushed a commit to johno/gatsby that referenced this issue Jul 17, 2019
@redallen @johno
Allow webpack loaders for relative imports (gatsbyjs#374)
439ae87 
* Allow webpack loaders for relative imports

* Clean loader path logic
This was referenced Apr 28, 2020
Open
Open
This was referenced Nov 9, 2022
Open
Open
@snyk-bot snyk-bot mentioned this issue Nov 30, 2022
Open
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
help wanted Issue with a clear description that the community can help with.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@KyleAMathews @savolai @nason