Create a new branch (from main) named after the Ember version range that will be supported by this branch.Makes sure you have a config/secrets.json file with the correct AWS credentials to push to S3.Skip this step if there are not new commits after the last release. Release a new version (See "Minor and major versions") if there are unreleased commits in main. Here are the steps to lock an inspector version: The Ember versions supported by the current inspector are indicated in the emberVersionsSupported array in package.json. It works by serving a different inspector version based on the current app's Ember version. This allows us to stop supporting old Ember versions in main without breaking the published inspector for old Ember apps. We can take a snapshot of the current inspector version to support a specific Ember version range. pnpm start To start the test server at localhost:4200/testing/tests.pnpm test To run the tests in the terminal.pnpm watch To watch the files and re-build in dist when anything changes (useful during development).pnpm build to build the files in the dist directory.Run pnpm install & pnpm add -g ember-cli to install the required modules. Javascript: ( function ( ) ( ) ) Building and Testing: Choose the dist/firefox/manifest.json file in the cloned repo.Visit about:debugging#/runtime/this-firefox in Firefox.Close and re-open developer tools if it's already open.Choose the dist/chrome folder in the cloned repo.run pnpm build to build the dist directory.Install the extension from the Chrome Web Store. Adds an Ember tab to the browser's Developer Tools that allows you to inspectĮmber objects in your application.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |