Move utility functions out of apollo-env, leaving polyfills.

The `apollo-env` package has a number of purposes today, including providing
polyfills for runtimes that lack more modern features, providing utility
functions (like, `createHash` that works on non-Node.js environments) and
offering some common predicate functions like `isNotNullOrUndefined` - a
method that we use in many places in the Apollo ecosystem.

The polyfills have proven useful on environments that necessitate them,
offering newer ECMAScript functionality in runtimes that don't yet have
them, but they're automatically loaded from the main module entry point of
this library, rather than being selectively enabled.  For example, it's not
uncommon to see `import 'apollo-env';` in other packages that rely on the
functionality.

It's this automatic eager loading of polyfills that proves to be problematic
when the _utilities_ and _predicate_ functions of this library come into
play though.  Imagine a package that merely needs to use a version of
`createHash` that simply falls back gracefully to a JavaScript version, or a
function that wants to utilize the useful `mapValues` function, but in a
circumstance where we - or our users - don't want to be subjected to the
nature of polyfills affecting the runtime (see related issues like
apollographql/apollo-server#2634).

Another circumstance that arises, which was the most motivating factor in
this case, is that the `apollo-env` package has consistently proven
difficult for bundlers to traverse, possibly because of the polyfills,
possibly because of the side-effects, possibly because of both!  However,
in my times trying to bundle our Apollo packages over the years, I've
encountered problems with Webpack, Snowpack, Rollup.js and now esbuild.

Most of these functions are small enough and simple enough that the
duplication cost isn't all that high.  For example, in my changes in this
commit, rather than paying the cost of relying on an other package for what
is basically a one-line function, I've just copied and pasted
`isNotNullOrUndefined` into a couple places where it is needed.
Furthermore, since most of the utilities that were being leveraged from
`apollo-env` were being leveraged _by_ the `apollo-graphql` package, I've
just moved those into that package instead.

Any runtimes that still necessitate polyfills like `Array.prototype.flat` or
`Array.prototype.flatMap` can still `import "apollo-env";` directly for
those side-effects to be applied to their runtme, and packages that just
need the utilities can rely on `apollo-graphql`.  Again though, most of
our packages are depending on both already so creating the more distinct
separation seems not-all-that-unreasonable.  Furthermore, while `apollo-env`
does also provide some `fetch` polyfills, once Node.js 12 becomes the minimum
version we support, I don't think we even need those polyfills anymore at all.

Author: abernix

packages/apollo-env/src/index.ts

@@ -2,4 +2,3 @@ import "./polyfills";
 
 export * from "./typescript-utility-types";
 export * from "./fetch";
-export * from "./utils";

packages/apollo-env/src/utils/index.ts

@@ -11,7 +11,6 @@
     "node": ">=6"
   },
   "dependencies": {
-    "apollo-env": "file:../apollo-env",
     "lodash.sortby": "^4.7.0"
   },
   "peerDependencies": {

packages/apollo-env/src/utils/predicates.ts

@@ -53,7 +53,6 @@
 // defaultOperationRegistrySignature, which are slightly different normalization
 // functions used in other contextes.
 import { DocumentNode } from "graphql";
-import { createHash } from "apollo-env";
 import {
   printWithReducedWhitespace,
   dropUnusedDefinitions,
@@ -62,6 +61,7 @@ import {
   removeAliases,
   hideLiterals
 } from "./transforms";
+import { createHash } from "./utilities/createHash";
 
 // The usage reporting signature function consists of removing extra whitespace,
 // sorting the AST in a deterministic manner, hiding literals, and removing

packages/apollo-graphql/package.json

@@ -30,7 +30,7 @@ import {
   UniqueDirectivesPerLocationRule,
   ValidationRule
 } from "graphql/validation";
-import { mapValues, isNotNullOrUndefined } from "apollo-env";
+import { mapValues } from "../utilities/mapValues";
 
 export interface GraphQLSchemaModule {
   typeDefs: DocumentNode;
@@ -295,3 +295,9 @@ export function addResolversToSchema(
     }
   }
 }
+
+function isNotNullOrUndefined<T>(
+  value: T | null | undefined
+): value is T {
+  return value !== null && typeof value !== "undefined";
+}

packages/apollo-graphql/src/operationId.ts

@@ -21,7 +21,7 @@ import {
   GraphQLInputObjectType,
   GraphQLInputFieldConfigMap
 } from "graphql";
-import { mapValues } from "apollo-env";
+import { mapValues } from "../utilities/mapValues";
 
 type TypeTransformer = (
   type: GraphQLNamedType