We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
With the new version of Fatina v3.0, the syntax of import slightly changed:
Typescript / ESM modules
import * as Fatina from 'fatina'; // become import Fatina from 'fatina';
CommonJS (Node)
var Fatina = require('fatina'); // become var Fatina = require('fatina').default;
Web / CDN Nothing change, still use global variable Fatina
Sorry for the modification, this default export really makes auto-completion and declaration support easier to manage.
The text was updated successfully, but these errors were encountered:
thanks, I was about to open issue about vscode auto-completion 😄
Sorry, something went wrong.
No branches or pull requests
Description
With the new version of Fatina v3.0, the syntax of import slightly changed:
Typescript / ESM modules
CommonJS (Node)
Web / CDN
Nothing change, still use global variable Fatina
Why ?
Sorry for the modification, this default export really makes auto-completion and declaration support easier to manage.
The text was updated successfully, but these errors were encountered: