jump to navigation

“emitted file Xyz.d.ts overwites a previously emitted file of the same name” May 1, 2020

Posted by kevinbe71 in Development, React, TypeScript, Uncategorized, Web Development.
Tags: , , , ,
add a comment

After making some recent changes and then upgrading rollup to 2.7.6 (from a 1.x release) I started seeing 2 of these warnings appear:

(!) The emitted file “actions\Xyz.d.ts” overwrites a previously emitted file of the same name.
(!) The emitted file “actions\Xyz.d.ts” overwrites a previously emitted file of the same name.

I used git bisect to quickly track down the commit that caused this issue and, fortunately, it was pretty obvious then:

I had 2 variations of imports of this file:
import * as Xyz from “./Xyz”;
import * as Xyz from “./xyz”;

This may not jump out to you immediately but the difference is a camelCase name vs a PascalCase name of the same file. The true file was called “xyz” but if you’re using Mac OS X or Windows then the compiler actually permits this. The newer version of rollup wasn’t letting things be… if wasn’t happy (which was a good thing)!

Nice surprise – Tortoise-Git Word Document Diff January 21, 2013

Posted by kevinbe71 in Beyond Compare, Development, Git, Microsoft Word, SCM Tools, Software.
Tags:
add a comment

Today I discovered a pretty neat feature of Git (in combination with Tortoise-Git)…

If you’re about to commit changes and those changes include a Microsoft Word document (*.docx), when you open up your diff tool it will instead open up Word in “merge documents” mode to show the differences. Β When it first happened I wasn’t sure whether it was Beyond Compare or Git doing it but after this search result (link below) I confirmed that it is indeed a feature of the Git Diff Tool.

http://xcafebabe.blogspot.com/2012/09/sexy-comparison-of-word-documents-with.html

BTW, I’ll take this opportunity to mention how well it all works with Scooter Software’s Beyond Compare thrown into the mix. πŸ™‚

Forced “Get Latest” Using Git January 11, 2012

Posted by kevinbe71 in SCM Tools.
Tags:
add a comment

If you’re used to other version control packages you may be familiar with “Get Latest” or forced checkouts etc. Well, Tortoise doesn’t seem to map this type of function… So you’ll have to delete the folder in question, drop to the Git bash command prompt and then type “git reset –hard HEAD” (there are actually 2 dashes here even though it may look like one!). That will make sure you have what’s in source control without any local changes.

Design a site like this with WordPress.com
Get started