Remove alias plugin, as tooling will eventually support aliases / "se…

…lf imports" via package.json exports https://nodejs.org/api/packages.html#packages_self_referencing_a_package_using_its_name

packages/addon-dev/sample-typescript-rollup.config.js

@@ -1,12 +1,9 @@
 import path from 'path';
 
-import alias from '@rollup/plugin-alias';
 import ts from 'rollup-plugin-ts';
 import { defineConfig } from 'rollup';
 import { Addon } from '@embroider/addon-dev/rollup';
 
-import packageJson from './package.json';
-
 const addon = new Addon({
   srcDir: 'src',
   destDir: 'dist',
@@ -32,27 +29,6 @@ export default defineConfig({
     // and updates an 'ember-addon.app-js' entry in your package.json
     addon.appReexports([...globallyAvailable]),
 
-    // Allow top-level imports (what folks are used to from v1 addons)
-    // During the build, anything referencing a top-level import will be
-    // replaced with a relative import.
-    // DANGER: it's somewhat easy to cause circular references with this tool
-    alias({
-      entries: [
-        {
-          find: '#types',
-          replacement: path.resolve('src', '-private', 'types.ts'),
-        },
-        {
-          find: packageJson.name,
-          replacement: path.resolve('src'),
-        },
-        {
-          find: `${packageJson.name}/(.*)`,
-          replacement: path.resolve('src/$1'),
-        },
-      ],
-    }),
-
     // This babel config should *not* apply presets or compile away ES modules.
     // It exists only to provide development niceties for you, like automatic
     // template colocation.