graphy.js | A collection of RDF libraries for JavaScript | Runtime Evironment library

According to the documentation of webpack/webpack-dev-server you should run webpack serve instead of webpack-dev-server.

Try replacing in your package.json:

D3 projections are all pretty similar. If one projection projects a given point correctly, chances are so does every other one. They take coordinates in decimal degrees and spit out coordinates in pixels and not much else. Consequently, your statement: "d3geoAlbersUsa projection projects the map of the USA at [0,0] which is off the coast of Africa." is incorrect. [0,0] in degrees is off the coast of Africa, [0,0] in pixels can be anywhere. D3 is giving you pixels, not degrees.

If you have features/tiles/raster that show Africa where the US is or vice versa, you have conflicting projections or coordinate systems, not a failure of d3.geoAlbersUsa.

Also, if you are mixing pre-projected geometry and unprojected geometry, you're making it too difficult: you'll need to ensure that the projections used to pre-project one geometry matches the projection used to project the second, which unless you use d3 to preproject the geometry offline somewhere will cause you some headaches.

If you have a csv with coordinates in decimal degrees and a geojson with the same, you can assume that the projection (and consequently, any paths) will be rendered consistently, and correctly (where correctly is not necessarily equivalent to as desired...).

Now d3.geoAlbersUsa is a bit of a special projection in that it is a composite projection combining several distinct projections (all Albers, while also shrinking Alaska down several times). It is calibrated to be centered on the US assuming a screen size of 960x600 pixels. You shouldn't need to alter the centering point, it has been set for you. The translate must be modified in your case, however, as this translates the projected coordinates. The default translate expects a container of 960x600 pixels. You want the translate to be equal to width/2,height/2, as you have. Trickier is the scale, the default scale is 1070, which extends the US across 960 pixels. This scale factor is linear, so we can use: 1070/960*width to create a new scale factor (assuming width is the limiting factor).

d3.geoMercator is more plain, but we need to center that projection properly because it isn't by default centered on the US. We can use:

Your typography.js file is adding a box-shadow to all elements:

Lets try updating some webpack configs.

Try updating node_modules/@angular-devkit/build-angular/src/angular-cli-files/models/webpack-configs/browser.js

Almost at the end of the file you will find plugins and node, update the value of node (which is false) to be {crypto: true, stream: true, fs: 'empty', net: 'empty'}.

You can also add a postinstall script in the package.json to updated that file after the package installation.

Forgot to wrap the mounted component with material UI MuiThemeProvider

Let me kick my answer off with a warning:

Disclaimer: I do not recommend doing this in production. This is intended for testing font pairings locally.

Once you have chosen your fonts, I suggest hosting webfonts on your domain to avoid hitting a remote CDN. You could use classic @font-face declarations, or Kyle Matthew's typefaces packages, for example.

Now, what you basically want to do is to import fonts client-side, to make it easy to try them out without rebuilding your site.

First, you'll need to get an embed link from your font hosting CDN (in your case, from Google Fonts). It will look like this:

Here is the simplified code. Keep the glob as is, it seems to be working fine. The issue is in how you parse the names from the list.

In this snippet you will see the issue of the blogSlugs from your code and the newBlogSlugs as a solution.

What the newBlogSlugs code does?

file.replace(/^.*[\\\/]/, '').split('.')[0]

Replace methods replaces all the path parts except the last one and we get "cupcakes.md". Then we split the string on the dot and use only the first part and get "cupcakes".

Reference @material-ui/core as a regular expression instead of a string. /^\@material\-ui\/core\/.*/ to match all imports that begin with the namespace in question.

Enzyme full dom mounting:

.find(selector) => ReactWrapper returns a wrapper, not a boolean