0.4.10

🎁 What's new?

• Basic support for front-end development using node.js and webpack module bundler.
  New projects now include webpack configuration and additional files, if either node is installed or --frontend is used. Node dependencies will automatically be installed. dfx build will run npm run build if a package.json file is present. Note that this feature is still experimental and additional functionality and documentation will be added soon.
• A new dfx upgrade command checks for the latest version and upgrades your dfx installation if a newer version of dfx is found.
• Creating a new project with dfx new will create a directory and folders with the corresponding name.
  Previously, you had to rename all of your source and canister directories from hello to your project name.
• You can specify the format of the configuration file output as json or text, with json being the default, using --format option with dfx config.
• Project naming restrictions have been added to ensure that project names are valid when used in JavaScript, Motoko, and other contexts.
  The most notable change you will find is there is no longer support for dashes -. All projects within the tutorials have been changed to use an underscore _.
• Motoko now supports pattern matching with type-annotated object fields.
  Pattern matching with type-annotated object fields is useful if you are writing a function that takes a record as input and the record fields so that you want to use the field names as bindings (local variable names). However, because type inference is not possible in this case, you must provide types for the fields.
• New tutorials have been added to provide additional guidance to new developers and include more sample code.

0.4.9

🎁 What's new?

• Query command will be deprecated, but can still be used in this release.
• Added cache subcommand and can defer dfx to cached version.
  The following cache subcommands are now available:
  ManageCache: Manages the dfx version cache
CacheDelete: Delete a specific versioned cache of dfx
CacheUnpack: Force unpacking the cache from current version
CacheList: List installed and used version
• Support variant for IDL deserialization
• You can now deserialize variant type to an abstract value type like IDLValue.

🛠 Issues fixed in this release:

• Query command will be deprecated, but can still be used in this release.
• dfx ide command renamed to _language-service
  Following release of dfx ide in V0.4.7, this command has been renamed to better reflect its intended use. This command command is meant to be run by editors to start a language service and will most likely not be used in a terminal. If desired, you can pass the --force-tty flag.
• Security flags fixed when installing dfx
  You will now be prompted to use TLS 1.3 if available, but --insecure flag can be used as a workaround.
• Support added for unknown read response to request-status.
  Previously an error was provided when requesting status and the client did not process the message.

0.4.7

🎁 What's new?

• You can now start the Motoko language services using dfx ide.
• Better support for IDL canister arguments, including:
  (1) Support for unicode escape, e.g. \u{10ffff}\0a
  (2) Number can be either decimal or hex with 0x prefix. Can insert _ in between digits, e.g. 1_000_000
  (3) Short-hand: omit null for variant; omit label for record.
• Oneway awaits. Previously, oneway shared functions could not await/try/throw from within their bodies.
• NEW colored logo! Try on a dark background for maximum pizzazz.

0.4.4

🎁 What's new?

• Wait flag has been removed: Default behavior is now to wait for a response and a new --async option enables you to get a request identifier and check on the results of your request later.
• dfx stop to stop dfx if it’s running in the background: It will stop the processes whether the client processes are running in the terminal or the background.
• Developer can refer to canister by name: Install or call by using the name defined for the canister in the project dfx.json file.
• Add support for argument to dfx build: Ignored in previous versions.

🛠 Issues fixed in this release:

• Failed build fixed for MacOS and Linux.
• Updated path in installer.
• Memory leak resolved.

0.4.1 (Test of stable release branch)

See changelog [to come] for notes. Bug fixes mainly.

0.4.0 (Alpha Launch)

See sdk.dfinity.org for full release notes.

DFX Demo

This release contains the standalone dfx, which understands all the things shown at the 0.3.0 demo.

To install the latest DFX, use:

curl https://hydra-int.dfinity.systems/latest/dfinity-ci-build/sdk/dfinity-sdk.packages.public-folder.x86_64-linux/public-folder/install.sh | sh

0.2.1

dfx

• Rename send command to call

0.2.0

dfx

The following commands may be executed in order:

A developer can start a node (i.e. locally on Linux or macOS)

$ cd examples/hello
$ dfx start

A developer can compile ActorScript into a Wasm module

$ dfx build
$ find build # view the contents of the build directory

A user can receive "Hello {name}" by calling a canister with an argument

$ dfx send http://localhost:8080 DFINITY
Hello, DFINITY!

---

Run kill $(pgrep nodemanager) && kill $(pgrep client) or similar when finished to stop the node.

0.1.0

dfx

A user can receive "Hello World" by calling a precompiled canister.

dfx http://10.129.10.113:8080
Hello, World!