Ember CLI blueprint for initializing a new TypeScript library, developing it using VSCode and deploying it to NPM.
$ npm install -g ember-cli
$ ember new -b libkit <package-name>
Write your library using .ts
files instead of .js
files and
libkit will take care of making things work.
The normal Ember CLI workflows work:
ember test -s
to run your tests in Node and in the browserember s
to serve your tests for use in a browser directlyember init
to upgrade devkitember build
and ember build -prod
to build your packageThe normal NPM workflows work too:
npm publish
to publish your package, including Node modules (in
CJS format), ES modules, and .d.ts
files for other TypeScript
consumersnpm test
to run the tests in CI modeIntegration with VSCode:
cmd-shift-b
to run TSLint and TypeScript type checkingf5
TDD
task)Good defaults that work with the rest of the workflow:
import ... from 'your-package';
works in Ember and
environments that support the "module"
key in
package.json
.All of these features should work on Windows (one of the main authors uses a Windows machine to develop these packages). We will prioritize any Windows bugs.