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
We experience a lot of fallout from changes to the NPM initializer. Occasionally when consumers scaffold a template with the initializer, their project template will break from some minor change. For example, we recently bumped @rei/cedar to 15. This major change renamed an asset we referenced in one of the templates, resulting in a build time error.
At a minimum, we should write an integration test that scaffolds and builds each template type. This will ensure changes to the initializer don't break downstream.
Once written, we should trigger these integration tests on remote push events with GitHub Actions.
The text was updated successfully, but these errors were encountered:
We experience a lot of fallout from changes to the NPM initializer. Occasionally when consumers scaffold a template with the initializer, their project template will break from some minor change. For example, we recently bumped
@rei/cedar
to 15. This major change renamed an asset we referenced in one of the templates, resulting in a build time error.At a minimum, we should write an integration test that scaffolds and builds each template type. This will ensure changes to the initializer don't break downstream.
Once written, we should trigger these integration tests on remote push events with GitHub Actions.
The text was updated successfully, but these errors were encountered: