Change view module resolution

[emmatown]

This pull request changes field type .views resolution from being path based to a module path.
This means instead of using require.resolve(...) to resolve your custom views, you will now use a path as though it was resolving from where keystone dev is run.

This additionally means you can use typical modules or packages without needing relative or absolute pathing workarounds.

For example, if you wanted to use the @keystone-6 text field views for your custom field type, you can now do that through canonical module resolution:

  fieldType({ ... })({
    input: { ... },
    output: graphql.field({ ... }),
    views: '@keystone-6/core/fields/types/text/views',
  })

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
keystone-next-docs	✅ Ready (Inspect)	Visit Preview	Aug 25, 2022 at 2:18AM (UTC)

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit d358281:

Sandbox	Source
@keystone-6/sandbox	Configuration