🗳️ Monitor your country, your city council or your organization promises and objectives
Home Page: https://democracywatcher.netlify.com
License: GNU General Public License v3.0
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/plugin-proposal-class-properties in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating history in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby in /yarn.lock:
Couldn't find any versions for "gatsby-plugin-netlify" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating prettier in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating chart.js in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/preset-es2015 in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/preset-react in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/plugin-proposal-object-rest-spread in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating i18n-js in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-source-filesystem in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-plugin-netlify in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby in /yarn.lock:
Couldn't find any versions for "gatsby-plugin-netlify" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating i18n-js in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-transformer-yaml in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-plugin-react-helmet in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby in /yarn.lock:
Couldn't find any versions for "gatsby-plugin-netlify" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating uuid in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating slugify in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-source-filesystem in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/plugin-proposal-object-rest-spread in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-transformer-yaml in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-source-filesystem in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-plugin-netlify in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating i18n-js in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating chart.js in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-plugin-react-helmet in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating history in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon-neat in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating slugify in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating react in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating @babel/preset-react in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating history in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating react-helmet in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating bourbon in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating prettier in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating react-helmet in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating react-helmet in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-source-filesystem in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating history in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
We should be able to configure (ideally from a YAML file) the following settings:
Github pages use a very basic webserver that doesn't work well with single page applications: it will return 404 errors if we try to load a page that is not the index directly.
However, there is a decent hack to work around this as mentioned here
This is a lightweight solution for deploying single page apps with GitHub Pages. You can easily deploy a React single page app with React Router <BrowserRouter />, like the one in the live example, or a single page app built with any frontend library or framework.
GitHub Pages doesn't natively support single page apps. When there is a fresh page load for a url like example.tld/foo, where /foo is a frontend route, the GitHub Pages server returns 404 because it knows nothing of /foo.
When the GitHub Pages server gets a request for a path defined with frontend routes, e.g. example.tld/foo, it returns a custom 404.html page. The custom 404.html page contains a script that takes the current url and converts the path and query string into just a query string, and then redirects the browser to the new url with only a query string and hash fragment. For example, example.tld/one/two?a=b&c=d#qwe, becomes example.tld/?p=/one/two&q=a=b~and~c=d#qwe.
The GitHub Pages server receives the new request, e.g. example.tld?p=/..., ignores the query string and hash fragment and returns the index.html file, which has a script that checks for a redirect in the query string before the single page app is loaded. If a redirect is present it is converted back into the correct url and added to the browser's history with window.history.replaceState(...), but the browser won't attempt to load the new url. When the single page app is loaded further down in the index.html file, the correct url will be waiting in the browser's history for the single page app to route accordingly. (Note that these redirects are only needed with fresh page loads, and not when navigating within the single page app once it's loaded).
A quick SEO note - while it's never good to have a 404 response, it appears based on Search Engine Land's testing that Google's crawler will treat the JavaScript window.location redirect in the 404.html file the same as a 301 redirect for its indexing. From my testing I can confirm that Google will index all pages without issue, the only caveat is that the redirect query is what Google indexes as the url. For example, the url example.tld/about will get indexed as example.tld/?p=/about. When the user clicks on the search result, the url will change back to example.tld/about once the site loads.
For general information on using GitHub Pages please see GitHub Pages Basics, note that pages can be User, Organization or Project Pages
Basic instructions - there are two things you need from this repo for your single page app to run on GitHub Pages
404.html file to your repo as is
username.github.io/repo-name), then you need to set segmentCount to 1 in the 404.html file in order to keep /repo-name in the path after the redirect.index.html file and add it to your index.html file
index.html fileDetailed instructions - using this repo as a boilerplate for a React single page app hosted with GitHub Pages
$ git clone https://github.com/rafrex/spa-github-pages.git).git directory (cd into the spa-github-pages directory and run $ rm -rf .git)$ git init in the spa-github-pages directory, and then $ git add . and $ git commit -m "Add SPA for GitHub Pages boilerplate" to initialize a fresh repositorymaster to gh-pages ($ git branch -m gh-pages), if this will be a User or Organization Pages site, then leave the branch name as master$ git remote add origin <your-new-github-repo-url>)spa-github-pages directory to anything you want (e.g. your-project-name)gh-pages branch of an existing repository
gh-pages for your existing repo ($ git checkout --orphan gh-pages), note that the gh-pages branch won't appear in the list of branches until you make your first commit.git directory) from the directory of your existing repo ($ git rm -rf .)spa-github-pages directory into your project's now empty directory ($ mv path/to/spa-github-pages/{.[!.],}* path/to/your-projects-directory)$ git add . and $ git commit -m "Add SPA for GitHub Pages boilerplate" to instantiate the gh-pages branchCNAME file with your custom domain, don't include http://, but do include a subdomain if desired, e.g. www or your-subdomainCNAME and/or A record with your DNS provider$ dig your-subdomain.your-domain.tld to make sure it's set up properly with your DNS (don't include http://)CNAME fileusername.github.io/repo-name):
segmentCount to 1 in the 404.html file in order to keep /repo-name in the path after the redirectrepo-name to the absolute path of assets in index.html
"/repo-name/build/bundle.js"repo-name as the basename, for example <BrowserRouter basename="/repo-name" />$ npm install to install React and other dependencies, and then run $ npm run build to update the build$ git add . and $ git commit -m "Update boilerplate for use with my domain" and then push to GitHub ($ git push origin gh-pages for Project Pages or $ git push origin master for User or Organization Pages) - the example site should now be live on your domainindex.html)index.html and the title in 404.html to your site's titleindex.html$ npm run build (this runs webpack -p for production) to update the build, then $ git commit and $ git push to make your changes liveI have included webpack-dev-server for testing changes locally. It can be accessed by running $ npm start (details below), or you can use your own dev setup by running $ webpack and serving the index.html file and the 404.html file for 404s. Note that webpack-dev-server automatically creates a new bundle whenever the source files change and serves the bundle from memory, so you'll never see the bundle as a file saved to disk.
$ npm start runs the start script in package.json, which runs the command $ webpack-dev-server --devtool eval-source-map --history-api-fallback --open
-devtool eval-source-map is for generating source maps in while in development--history-api-fallback allows for frontend routing and will serve index.html when the requested file can't be found--open will open automatically open the site in your browserwebpack-dev-server will serve index.html at http://localhost:8080 (port 8080 is the default). Note that you must load the index.html from the server and not just open it directly in the browser or the scripts won't load..nojekyll file in this repo turns off Jekyll for GitHub PagesDependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby-transformer-yaml in /yarn.lock:
Couldn't find any versions for "gatsby" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Coffeescript files are still present as legacy code. They should all be migrated to JSX
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby in /yarn.lock:
Couldn't find any versions for "gatsby-plugin-netlify" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
Dependabot can't resolve your JavaScript dependency files.
As a result, Dependabot couldn't update your dependencies.
The error Dependabot encountered was:
Error whilst updating gatsby in /yarn.lock:
Couldn't find any versions for "gatsby-plugin-netlify" that matches "next"
If you think the above is an error on Dependabot's side please don't hesitate to get in touch - we'll do whatever we can to fix it.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.