Add smoke-tests for types, build, etc

[NullVoxPopuli]

Description

Supersedes: #9631
Resolves: #9630

ember-data / warp-drive has enough going on it to warrant testing if new projects in various scenarios will work:

• linting
• type checking
• building
• a basic test

Unblocks:

• [BUGFIX release]: tsconfig.json referenced paths to types instead of imports ember-cli/ember-cli#10612
  • Fixes: 6.1, ember-data TS config is broken in monorepo when using npm or yarn@1 ember-cli/ember-cli#10611

Notes for the release

fix: tsconfig.json#compilerOptions#types can now use the package.json#exports paths, example:

"compilerOptions": {
  "types": [
      "ember-source/types",
      "ember-data/unstable-preview-types",
      "@ember-data/store/unstable-preview-types",
      "@ember-data/adapter/unstable-preview-types",
      "@ember-data/graph/unstable-preview-types",
      "@ember-data/json-api/unstable-preview-types",
      "@ember-data/legacy-compat/unstable-preview-types",
      "@ember-data/request/unstable-preview-types",
      "@ember-data/request-utils/unstable-preview-types",
      "@ember-data/model/unstable-preview-types",
      "@ember-data/serializer/unstable-preview-types",
      "@ember-data/tracking/unstable-preview-types",
      "@warp-drive/core-types/unstable-preview-types"
  ]
}

Notes for review

NPM is not as understanding when it comes to tarballs:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @ember-data/[email protected]
npm error Found: @ember-data/[email protected]
npm error node_modules/@ember-data/store
npm error   dev @ember-data/store@"file:./ember-data-store-5.4.0-alpha.126.tgz" from the root project
npm error   peer @ember-data/store@"*" from @ember-data/[email protected]
npm error   node_modules/@ember-data/adapter
npm error     dev @ember-data/adapter@"file:./ember-data-adapter-5.4.0-alpha.126.tgz" from the root project
npm error     @ember-data/adapter@"*" from [email protected]
npm error     node_modules/ember-data
npm error       dev ember-data@"file:./ember-data-5.4.0-alpha.126.tgz" from the root project
npm error   7 more (@ember-data/debug, @ember-data/graph, ...)
npm error
npm error Could not resolve dependency:
npm error peer @ember-data/store@"^4.12.0 || ^5.0.0" from @ember-data/[email protected]
npm error node_modules/@ember-data/rest
npm error   dev @ember-data/rest@"file:./ember-data-rest-5.4.0-alpha.126.tgz" from the root project
npm error
npm error Conflicting peer dependency: @ember-data/[email protected]
npm error node_modules/@ember-data/store
npm error   peer @ember-data/store@"^4.12.0 || ^5.0.0" from @ember-data/[email protected]
npm error   node_modules/@ember-data/rest
npm error     dev @ember-data/rest@"file:./ember-data-rest-5.4.0-alpha.126.tgz" from the root project

the install-time peer checking here isn't as important as the post-install peer checking -- we don't want npm using the versions from package.json exactly, but the versions installed the specifiers in the package.json -- kinda surprised they have this bug, tbh

[NullVoxPopuli]

@runspired somethingy goofy is happening with the types.

I probably did something weird, but I'm consistently getting stuff like:

/// <reference path="./data-adapter.d.ts" />
/// <reference path="./_app_/data-adapter.d.ts" />
declare module '@ember-data/debug' {
  /// <reference path="./data-adapter.d.ts" />
  /// <reference path="./_app_/data-adapter.d.ts" />
  module '@ember-data/debug' {
    /// <reference path="./data-adapter.d.ts" />
    /// <reference path="./_app_/data-adapter.d.ts" />
    module '@ember-data/debug' {
      /// <reference path="./data-adapter.d.ts" />
      /// <reference path="./_app_/data-adapter.d.ts" />
      module '@ember-data/debug' {
        /// <reference path="./data-adapter.d.ts" />
        /// <reference path="./_app_/data-adapter.d.ts" />
        module '@ember-data/debug' {
          /// <reference path="./data-adapter.d.ts" />
          /// <reference path="./_app_/data-adapter.d.ts" />
          module '@ember-data/debug' {
            /// <reference path="./data-adapter.d.ts" />
            /// <reference path="./_app_/data-adapter.d.ts" />
            module '@ember-data/debug' {
              /// <reference path="./data-adapter.d.ts" />
              /// <reference path="./_app_/data-adapter.d.ts" />
              module '@ember-data/debug' {
                /// <reference path="./data-adapter.d.ts" />
                /// <reference path="./_app_/data-adapter.d.ts" />
                module '@ember-data/debug' {
                  /// <reference path="./data-adapter.d.ts" />
                  /// <reference path="./_app_/data-adapter.d.ts" />
                  module '@ember-data/debug' {
                    export { default } from '@ember-data/debug/data-adapter';
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}
//# sourceMappingURL=index.d.ts.map

how is the build supposed to happen?
I'm doing:

• pnpm install (in the ci workflow)
• pnpm prepare (here)
• generateTarballs (in buildAll)

which doesn't quite seem like the right incantations.
CI does this, which starts with a cleaner slate than I am:

• https://github.com/emberjs/data/actions/runs/12719039922/job/35458531552?pr=9633#step:4:40
• null characters?

[NullVoxPopuli]

oh! this is caused by bad output in turbo cache

[NullVoxPopuli]

the transformation of this output needs to either run through turbo, after prior commands have finished (so that caching has the correct non-modified output), or we need to make the declare-module wrapping idempotent (which is the direction i'm leaning)

[NullVoxPopuli]

Without these changes not all node_modules directories have the right bins in node_modules -- for example, @warp-drive/ember did not have glint, and would fail to build its types