Skip to content

Remove Path Aliasing #147

Open
@kevinfodness

Description

@kevinfodness

Description

Path aliasing causes more problems than it solves, and needs to be configured among several different pieces of technology (TypeScript, Webpack, ESLint, Jest ...) and it would be simpler to remove it, even though developers would have to specify relative paths to files they are including.

Use Case

When a user uses this framework, its configuration should be as simple as possible.

Acceptance Criteria

  • Remove compilerOptions.paths from tsconfig.json
  • Remove moduleNameMapper from jest.config.ts
  • Update paths in plugin-templates directory to be relative from where they will be placed in the plugin when the configure script is run rather than using the * path shortcut
  • Ensure that both Remove Path Aliasing create-wordpress-theme#41 and Remove Path Aliasing create-wordpress-plugin#444 are completed and new releases have been published for both create-wordpress-plugin and create-wordpress-theme that contain these fixes
  • Confirm resulting paths are correct when running the configure script using the newly released plugin and theme (lint checks pass, build passes)

Metadata

Metadata

Assignees

No one assigned

    Labels

    ci/cdPR checks, deploys, automationjavascriptRequires understanding JavaScript

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions