Sarah Federman sarahbethfederman

Known issues (to follow up on)

Sometimes after changing content in contentful you may get a TypeError: Cannot read property 'internal' of undefined error. The only fix I've found for this is to unpublish all contentful component pages, and republish them ~4 at a time, building each time. Relevant issue here: contentful/rich-text#53 gatsbyjs/gatsby#6949

Embedded entries don't resolve when using gatsby develop: contentful/rich-text#46 gatsbyjs/gatsby#10592 gatsbyjs/gatsby#9821

	<script>// Provides explicit indication of elements receiving focus through keyboard interaction rather than mouse or touch.
	(function(document) {
	var NAVIGATION_KEYS = [
	'Tab',
	'ArrowUp',
	'ArrowRight',
	'ArrowDown',
	'ArrowLeft',
	'Home',
	'End',

	import React from 'react';

	const NAVIGATION_KEYS = [
	'Tab',
	'ArrowUp',
	'ArrowRight',
	'ArrowDown',
	'ArrowLeft',
	'Home',
	'End',

	Search Bar*

	Inactive*
	focused -> Active

	Active
	canceled -> Inactive
	typed -> Text Entry

	Empty*

	Dropdown*
	Inactive*
	focus -> Focused
	click -> Open

	Focused
	down arrow key -> Open

	Open
	arrow key -> Navigating

	import React from 'react';
	import { Link as GatsbyLink } from 'gatsby';
	import * as deepmerge from 'deepmerge';

	import { INLINES, BLOCKS, MARKS } from '@contentful/rich-text-types';
	import { documentToJSX } from './../scripts/documentToJSX';
	import { getEntry } from './../scripts/getContentfulEntry';

	const Link = ({ children, to, activeClassName, ...other }) => {
	const internal = /^\/(?!\/)/.test(to);


	"pkg-a@<VERSION_RANGE>"
	version: version of pkg-a that we resolve to, aka what ends up being bundled
	dependencies:
	pkg-b: the range that is specified in pkg-a's package.json

	"pkg-b@<VERSION_RANGE>"
	version: the version that packages depending on pkg-b@<VERSION_RANGE> get


	"[email protected]"
	version "1.0.0"
	dependencies:
	pkg-b "^2.0.0"

	"[email protected]"
	version "1.0.0"
	dependencies:
	pkg-b "^2.0.0"