@iabtcf/core: Remove typescript and global from dependencies
See original GitHub issueI would like to see typescript
moved from dependencies
to devDependencies
so typescript
is not installed on every project that’s using this package. This dependency alone is taking 50mb of disk space and causing a major slow down over Travis CI against the version without @iabtcf/core.
Also, global
dependency seems to not be used anywhere as well but it’s being installed.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:9
Top Results From Across the Web
Unable to uninstall typescript globally through npm
I've installed typescript 2.4.1 on my system globally (tsc -v gives me version 2.4.1). I want to uninstall it as I want to...
Read more >Guide to disable typescript and remove dependencies #339
I have reviewed this template and provide a list of necessary steps to completely remove all traces of TS. Most of these steps...
Read more >Uninstalling packages and dependencies - npm Docs
To uninstall an unscoped global package, on the command line, use the uninstall command with the -g flag. Include the scope if the...
Read more >Documentation - Global .d.ts - TypeScript
Many libraries simply expose one or more global variables for use. ... that are small and require the DOM (or have no dependencies)...
Read more >Managing Global Variable Dependencies - TechDocs
While monitoring an Application generation in the Monitor view, you can set up, edit, remove, and drop variable dependencies and reset the time ......
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 Free
Top 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
@dmdabbs Yes but I’d like this to be considered in the next release instead, so I have the proper amount of time to look through it.
Hi guys,
This issue will be a part of the 1.2.2 release as well as the current pending PRs. I won’t be able to attend to this issue or the current pending PRs for a couple of weeks at least since I have internal work that I need to do.
If anyone makes a PR before then, great, otherwise I will address it in a couple of weeks.