You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--no-frozen-lockfile or --no-lockfile, (I think already doing), obvious, we're changing deps (noted because when you set buildManagerOptions, you override)
--ignore-scripts, because folks who use prepareand use typescript will have a failing build. we do not want to re-build the addon during ember-try's install.
for example, if someone is relying on prepare behavior to build their addon:
try-scenarios:
timeout-minutes: 10name: "Try: ${{ matrix.ember-try-scenario }}"runs-on: ubuntu-lateststrategy:
# ...steps:
- uses: actions/checkout@v4
- uses: pnpm/action-setup@v4
- uses: actions/setup-node@v4with:
cache: pnpm# with prepare the addon builds with correct types, deps, etc
- run: pnpm install # however, today, with prepare, ember-try rebuilds it, but with incorrect dependencies (due to the ember-try config)# and potential repo-configurations to get around peer problems# such as public-hoist-pattern=ember-source
- working-directory: test-apprun: node_modules/.bin/ember try:one ${{ matrix.ember-try-scenario }} --skip-cleanup
The text was updated successfully, but these errors were encountered:
--no-frozen-lockfile or --no-lockfile, (I think already doing), obvious, we're changing deps (noted because when you set buildManagerOptions, you override)
--ignore-scripts, because folks who use
prepare
and use typescript will have a failing build. we do not want to re-build the addon during ember-try's install.for example, if someone is relying on
prepare
behavior to build their addon:The text was updated successfully, but these errors were encountered: