Empower doesn't allow you to import legacy data from other sources (like Mint) or input manual transactions such as cash. The latter isn't important to me, but the former certainly is. I have 16 years of transaction data in Mint that I want to preserve.

先在 Evernote 中選擇需要的筆記、記事本，匯出成 enex 檔案。

The conversation will no longer be accessible via the shared link, but if a user imported the conversation into their chat history, deleting your link will not remove the conversation from their chat history.

I used SjoerdV / ConvertOneNote2MarkDown PowerShell script. The key is running PowerShell and OneNote as Administrator.It will crash a bunch of times depending on the size of your OneNote repository. However, if you keep restarting the program as administrator it seems to start back were it left off.Here are my notes: https://www.dropbox.com/s/au66hamcv71sggk/202211151246%20OneNote%20to%20Markdown%20Procedure.pdf?dl=0

The final piece that's pushing the two first crucial changes over the paradigm hill is import maps. They allow the use of logical references for modules in ES6 (also known as ESM), rather than explicit file references.

Today, many web developers are even using JavaScript's native module syntax, but combining it with bare import specifiers, thus making their code unable to run on the web without per-application, ahead-of-time modification. We'd like to solve that, and bring these benefits to the web.

From my point of view, this approach will help you to write cleaner code. Also, it will help to maintain the project. For instance, moving a file from the current directory to another will cause fewer problems, because every file uses an absolute path instead of a relative one. Last but not least, it helps you during development.

import * as utils from '../../../../../../../shared/utils';

Saying that web devs used to be fine with relative imports is like saying that human beings used to be fine living without refrigerators. Sure we did. But was it better than it is now? No. No, it wasn't.

PROJECT IS NOT EU FRIENDLY

We will dispatch rewards from our factory to our FOUR 3rd party fulfillment centers, to keep things as friendly* as possible worldwide in accordance with all worldwide laws. *"Friendly" to us means: We will collect and pay VAT/Taxes upon importing to our  fulfilment centers on everyone's behalf so we can send your rewards DDP vs DAP.  If we were not "Friendly" - we would send games direct (DAP) and you would have to pay VAT and admin fees as well as a postal fee to "pick up" your reward locally - vs DDP where that is all done for you and the reward is delivered to your doorstep, "friendly".  It costs lots of money to ship 4 containers to 4 different fulfilment centers - but we do that in an effort to help our backers and to be *friendly.

Importing/Copying grading schemes from one course to another

@import url() is a runtime CSS statement, not a Sass @import module.

You can either use require to bypass typescript special import.

Everyone working in a TypeScript project that grows beyond a certains limit will eventually experience the situation commonly described as path hell, the snippet below is an example of such hell.

No more shit-coding paths in Node like so:

I was reading about path-mapping in tsconfig.json and I wanted to use it to avoid using the following ugly paths:

However, I just went through the same exercise of moving from relative paths everywhere to module paths.

The rule is written @forward "<url>". It loads the module at the given URL just like @use, but it makes the public members of the loaded module available to users of your module as though they were defined directly in your module. Those members aren’t available in your module, though—if you want that, you’ll need to write a @use rule as well.

The new @use is similar to @import. but has some notable differences:

In brief, @import is being replaced with more explicit @use and @forward rules. Over the next few years Sass @import will be deprecated, and then removed.

When you use a function like color(). it’s impossible to know exactly where it was defined. Which @import does it come from?

Unlike some other languages, Sass doesn’t require that you use ./ for relative imports. Relative imports are always available.

We’ve written a migration tool that automatically converts most @import-based code to @use-based code in a flash.

The @import rule has a number of serious issues:

The sass-loader uses Sass's custom importer feature to pass all queries to the Webpack resolving engine. Thus you can import your Sass modules from node_modules. Just prepend them with a ~ to tell Webpack that this is not a relative import: @import '~bootstrap';

Maybe of interest for some readers here: With your plugin, it's also straightforward to import the "tweets.csv" file from the official Twitter archive, which contains all the tweets (and a lot of metadata) from one's personal account. Still don't know what to do with this in TiddlyWiki, but there is certainly potential...

Now only the defined subpath in "exports" can be imported by a consumer:

Even though it works much like a function, import() is an operator

The module specifier is always fixed. That is, you can’t change what you import depending on a condition. And you can’t assemble a specifier dynamically.

To make this even easier, you can also simply import @testing-library/react/dont-cleanup-after-each which will do the same thing.

There is a new specification which is called a dynamic import for ES modules.