Duncan Walker sir-dunxalot

First you have to define the scalar type in the GraphQL schema:

scalar Date

Then you have to provide a resolver for the scalar type. Here's an example implementation using Luxon:

import { DateTime } from 'luxon';

makeExecutableSchema({

If you enjoyed reading this, I'm intending to do more blogging like this over here: https://cdgd.tech

This is not a complaint about Webpack or v4 in any way. This is just a record of my process trying it out so I could provide feedback to the webpack team

Hmm... I don't see any docs for 4.0 on https://webpack.js.org. I guess I'll just wing it. All I need to do is npm i -D webpack@next, right?

+ [email protected]

Forking and patching npm modules from a monorepo

Commonly, npm modules are source controlled using a single dedicated repo for each module. When forking and patching such an existing npm module, typical approaches are either:

reference a specific git commit in your forked repo

    "dependencies": {
        "patchedmodule": "git+https://github.com/myuser/patchedmodule.git#mypatch"
    }

reference a downloadable tarball containing the same, as described in this post on {debuggable}

Converting libraries to Ember CLI addons

In this guide we will cover two main cases:

Ember specific library
vendor library

Ember library

The Ember library will assume that Ember has already ben loaded (higher in the loading order) and thus will assume it has access to the Ember API.

	<!DOCTYPE html>
	<html>
	<head>
	<script>
	var data
	var formId = 'form'

	function drawForm() {
	if (!data) return
	var outputEl = document.getElementById(formId);

	app.registry.add('css', 'broccoli-compass', 'scss', {
	toTree: function(tree, inputPath, outputPath, options) {
	// broccoli-compass doesn't like leading slashes
	if (inputPath[0] === '/') { inputPath = inputPath.slice(1); }

	tree = mergeTrees([
	tree,
	'public'
	], {
	description: 'TreeMerger (stylesAndVendorAndPublic)'

	/**
	* Polyfill for "fixing" IE's lack of support (IE < 9) for applying slice
	* on host objects like NamedNodeMap, NodeList, and HTMLCollection
	* (technically, since host objects are implementation-dependent,
	* IE doesn't need to work this way). Also works on strings,
	* fixes IE to allow an explicit undefined for the 2nd argument
	* (as in Firefox), and prevents errors when called on other
	* DOM objects.
	* @license MIT, GPL, do whatever you want
	-* @see https://gist.github.com/brettz9/6093105