Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

transpile UI modules on publish

Description

Summary: transpile packages on publish, with source maps, so the bundling step doesn’t have to handle this. transpile-on-publish is SOP in the JS ecosystem and we should follow suit.

Details: Replaces

  • update package.json such that:

    • main points to dist/index.js (or whatever the appropriate file is)

    • files lists the array of files to include, limited to dist, translations, assets, README.md, LICENSE, CONTRIBUTING.md, and CHANGELOG.md.

    • scripts contains a prepare entry like stripes transpile or stripes transpile --files ./lib

  • move all code files from . into ./src or ./lib

Environment

None

Potential Workaround

None
12% Done
Loading...

Checklist

hide

Activity

Show:

Zak Burke February 3, 2025 at 9:22 PM

yarn workspaces run <command> runs a command across all packages in a workspace, e.g. so that you could run yarn build-watch to run every repo’s build-watch command, updating their dist directories on each change. pnpm’s --recursive and nx’s watch --all works similarly.

It isn’t clear if this command would need to exist at the workspace level (and thus require more formal workspace handling) or the platform-level (in which case we could just add it to the platform).

Details

Assignee

Reporter

Priority

Development Team

None

Epic Name

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 14, 2025 at 6:32 PM
Updated February 3, 2025 at 9:22 PM
TestRail: Cases
TestRail: Runs