Do not publish .ts files on npmjs.org
See original GitHub issueHi,
Apparently, angular2-notifications
is published on npmjs.org with its ts
files.
This is a bad practice according to (at least) angular-cli people (see https://github.com/angular/angular-cli/issues/4675#issuecomment-285694210).
It would be great if the ts
files were removed in future releases and optionally for the latest release too 😃
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:13 (5 by maintainers)
Top Results From Across the Web
Documentation - Publishing - TypeScript
If your types are generated by your source code, publish the types with your source code. Both TypeScript and JavaScript projects can generate...
Read more >Do not publish ts sources to npm · Issue #440 - GitHub
Do not publish ts sources to npm #440 ... It's a much better idea to publish and consume the .d.ts files if what...
Read more >index.d.ts file not published to NPM - Stack Overflow
When I build this project, the TS compiler generates the .d.ts files as expected, however, these files are not published on NPM and...
Read more >The 30-second guide to publishing a TypeScript package to ...
Then go to another folder and npm link <your package name> . Go into a .ts file and import your package by name...
Read more >In-depth guide on creating and publishing NPM with typescript
Ignore the compiled code in GIT. Usually, you do not want auto-generated files under your source control except for package-lock.json, as they ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The latest version no longer publishes .ts files
Also, Angular CLI incremental builds using
ng serve
seems to cause full angular2-notifications rebuild on any change. Maybe I’m wrong but that’s what I always see: