Error
Help
Upgrading
What changed in each release, what to do when you upgrade, and how wf migrate carries an older project forward.
This page says what each release asks of your project when you upgrade, newest first, from 7.0 back to WebFluent 2.
The policy behind it: a release should ask nothing of a project that works. When one does ask, it is because the old behaviour shipped a broken page, and the compiler then names every place that needs a change, with a code, instead of leaving you to find them in the browser. Most rows of the table below say "Nothing"; the others say which findings to look for.
The full notes for every release are in RELEASE_NOTES.md. This page keeps only what an upgrade asks of you:
- Install a newer version
- Upgrade a project
- The notes for each release, from 7.0 back to WebFluent 2
At a glance
| Release | What to do |
|---|---|
|
Run |
|
|
Nothing; a component named like a built-in now draws the project's own ( |
|
|
Run |
|
|
Run |
|
| Nothing | |
|
Run |
|
|
Run |
|
|
Run |
|
|
Separate style declarations with a newline or |
|
|
Nothing; a |
|
| Nothing | |
|
Rename any declaration that takes a name the language has ( |
|
|
Handle |
|
|
Run |
|
|
Run |
|
|
Nothing; rotate any secret a 4.0 build put in |
|
|
Run |
|
| The current grammar; nothing beyond 4.0 | |
|
Run |
Install a newer version
To upgrade the compiler, run the installer again — it replaces the binary in place — or, if you installed with Rust:
$ cargo install webfluent --force
wf --version says which version you have. Update wf-lsp and the editor extension at the same time: the language server is built from the same compiler, and an older one reports what the new wf does not (Troubleshooting).
Upgrade a project
After installing, bring each project forward:
- Read this page's notes for every release between the version the project last built with and the new one.
- Run
wf check. It writes nothing, and every finding names its code, its place and what to do. - Run
wf test. If snapshots changed, look at each difference, then runwf test --update. - Build, and load the result with
wf verify.
7.0
7.0 is strict, with no setting that turns it off: every value has a type the program can name, and a service is a contract whose calls answer with a result. What 6.x accepted and 7.0 refuses is an error with its fix, and wf migrate applies those fixes at once:
$ wf migrate --check # what it would rewrite, and nothing written
$ wf migrate
It rewrites the request forms 6.x had (N08): fetch(…) into http.get(…), a read's loading, error(e) and ready(v) arms into .loading, .failed(e) and .loaded(v), .data into .value, on: into refresh:, an endpoint's -> T into -> T!, a path's :id into {id}, at where an endpoint had none, headers { } into middleware [header(…)]. It declares what each state holds (T25), what each action returns and fails with (T26, N03), each parameter's type (T32), and JSDoc for a script function .wf calls (T31); it writes the comparison a condition meant (T29), a splice for text joined to a number with + (T18: "+" + n becomes "+{n}"), a splice or a unit where a value was converted (T34), try where a result's value is wanted, and an error enum's http case (N12). It runs until nothing is left to fix, then lists, by place, every error a person decides — a on request hook to write as a middleware, a paginate: to move onto its endpoint. A second run finds nothing.
Changes that need no edit, which it states:
- A
POSTorPATCHis retried, or replayed offline, only when its endpoint is markedidempotent. - Nothing is cached unless the server's
Cache-Controlor the contract says so. - Every answer is held to its declared type, deployed too: a server that does not keep its contract now fails as
.decode(at, message).
Any and Map are no longer types: written as one, each is an error (T23, T24), and wf migrate writes Json in its place — a record or a dictionary says more, where you know what it holds. lints and // wf-allow cannot lower or accept the typing codes or the request codes that are errors, and T20 — a list or a record shown as text — is an error now. A service described by an OpenAPI spec is best kept as files: wf api add openapi.json (see Call a service from its OpenAPI spec).
6.2
6.2 adds some sixty built-ins and makes the existing ones work by keyboard, screen reader, touch and right to left. Nothing in a project needs a change. Your project may notice these:
- A component of your own wins over a built-in of its name. It used to be the other way: the built-in was drawn and your component never was.
V11is now information, saying the built-in cannot be placed there. - A
Buttonwhoseon clickcalls an async action is busy until the call ends, and a call with the arguments of one still running joins it, so a double click submits once. Nothing is written for either.
6.1
6.1 sends much less: the runtime ships only what a program reaches, and the styles only what it draws on. Your project may notice these:
T10on anapiendpoint called with positional arguments. It built, and sent the first value as the call's map; write the call by name (Backend.signUp(body: { … })).E111inwf checkfor a themewebfluent.app.jsonnames and no file declares, which onlywf buildreported before.R05when a page and its translation are both in the site's language: a page with nolang:is inmeta.lang. Setmeta.langto the language those pages are written in, or give the pagelang:.- The router's box is a
divwhen the program draws its ownmain(role: "main"); its id is stillwf-main. - A script that calls the runtime by a name built at run time (a
WF[name]call) may find the function left out: set"build": { "runtime": "full" }.
6.0
6.0 lets a page be in a language of its own (lang:) and name the page it translates (translates:). Your project may notice these:
- No more
?lang=alternates. A project with severali18n.localeslisted a?lang=<code>address per locale as anhreflangalternate. Each served the default locale's HTML with the bare address as its canonical, so search engines filed them as duplicates and ignored the set. They are gone; a?lang=link still opens the page in that locale. To have each language indexed, write its pages withlang:andtranslates:(A page in its own language). - Every page's JSON-LD names its language,
inLanguage. wf renderandTemplateuse the page'slang:when--langorwith_langis not given; a page without one is stillen.- A word
langortranslatesin a page header is the new option when it takes a string or a page name. A route parameter of that name is still one:lang: String. - A build stays in its project. A
build.outputoutside the project is refused unlesswf buildorwf checkis given--allow-output-outside. - A
public_envname without thePUBLIC_prefix takes its value from the config or.env, and from the shell only whenWF_ALLOW_SHELL_ENVnames it. wf servelistens on this machine only. To reach it from a phone, runwf serve --host 0.0.0.0.navigate()stays on the site. An address on another origin is refused; leave the site with aLink.- What used to be clamped is refused: a status code past 599 or a fractional one, a negative
Carousel(interval:)(T01), and nesting past 100 levels (E120).
Run wf check.
A program that uses the webfluent crate is what 6.0 breaks:
- the compiler's internal modules need
features = ["internals"]; - a path moved to its layer (
webfluent::fmtiswebfluent::syntax::fmt); - a
matchon a public enum needs a_arm; - an error is built with
WebFluentError::io(…)and the like.
The release notes list them all.
5.14 and 5.13
Nothing to change. 5.14 builds a project to the same bytes as 5.13 did; 5.13 corrected the reference that wf init writes into a new project as AGENTS.md, so copy it again into a project made before it, or run wf init in a scratch folder and take its copy.
5.12
5.12 adds names in any script and translation by a project's own words, and makes every name a program binds its own. Your project may notice these:
- A store member may not be named like what every object has.
valueOf,toString,constructorand the other names every JavaScript object has areE118as a store's member, because the page threw as soon as it drew one. Rename the member. The same names now work as a component's props;__proto__as a prop isE118. - A test file may not declare a name the project declares. The two were one name on the test's page, and every browser test failed with a SyntaxError. It is now
E102at the test's declaration. Rename the test's own. T06is reported at the member's name. "Storehas no memberx" underlinesx, notStore. A tool that reads the line and column sees the new place.output_type: "static"pre-renders every page, asssg: truedoes. It used to build a single-page app. A project that set it and relied on that sets"spa"instead.- WebP is lossy at
build.media.quality, and a file no smaller than its original is not written. Pictures are smaller; a width that saved nothing is served from the original. - A name that clashed now works. A program's own name that was one of the generated code's, or a browser global's, used to read the wrong value; it reads its own now. A page that leaned on the wrong value changes.
Run wf check, then wf test.
5.11
5.11 adds to the language and fixes what an editor built on it found. Your project may notice these:
- A gesture on a component needs one element to land on.
drag:,dropValue:,on receive(d),on longpressand the rest, written on a component's call, used to throw at run time. They now land on the component's root element. A component whose body is anif, afor, amatchor several elements has no root, and the call is the new errorC07. To fix it, wrap the body in oneStackorRow. - A handler names at most what its event sends.
on menu(key, x, y)now reads each value that a component'sevent menu(…)sends. A name past the last one isT22. A DOM event sends only the event, soon click(e, x)isT22too. - A test file's declarations are its own. A
const, a component or a type written beside the tests in one file undertests/is no longer seen by another file's tests. Two files may now declare the same name. A file that used another file'sconstdeclares it itself, or moves it undersrc/. - A test names a control as a reader hears it. What is
aria-hidden(a menu item's shortcut, a glyph) is not part of the name, and a submenu's entry is its label without its items.click "Paste Ctrl+V"is nowclick "Paste", andclick "File"opens aMenu.Sub(label: "File").A15no longer counts anaria-hiddenglyph as part of a control's visible label either. - A block handed to a component reads the names where it was written in
wf testand the template engine, as the live page and the pre-rendered page already did. A snapshot that showed the inner component's value of a shared name changes. - A
Menu.Item'sclass:is added beside the menu's own, where it used to replace it, so the item keeps its padding and its shortcut column. A style that made up for the lost class can go. - A method of a receiver's own wins over a helper of the same name.
x.last(k)on a value with alastmethod of its own calls that method with every argument, where it used to call the list helper. A store's action named like a helper (preview,first,take…), called from another store, runs that action.
Run wf check, then wf test --update once you have read what the new snapshots show.
5.10
5.10 makes pages, pre-rendered pages and tests do what this guide says. Your project may notice the changes below. Run wf check after upgrading.
Layout and look
- Column spans leave room for the gap. A
Columnin aRowwith a gap is narrower by its share of the gap, and spans that add up to 12 sit on one line instead of wrapping the last. A layout that made up for the old behaviour, such asspan: 8besidespan: 3, now leaves a space; give it back its4. The spans read the gap from--wf-gap, whichgap:sets, so a gap your own CSS gives aRow(style { gap: 4px }) needs--wf-gap: 4pxbeside it. A PDF now lays aColumnout at itsspan:, and reads acalc()of a percentage and points against the box it lands in, as a browser does. - The
Navbartakes the theme's surface and text colours, so a dark or custom theme no longer gets a white bar. - A keyed list slides only the items whose index changes. An item that keeps its index while its place on screen moves now jumps there.
- A
Splitter'sreset:is written as given, not clamped tomin:andmax:, and the first drag or key press moves from the edge as drawn.
Controls and forms
- A
Menu'slabel:names its list, not its button. The button says whattrigger:says.Menu(label: "File")with neithertrigger:norvisible:now draws a button that says Menu; writetrigger: "File". A menu thatvisible:opens no longer draws a button. ADropdown'slabel:is still its button. - A
Formwithoutbind:asks thevalidaterules of its page or component beforeon submit, and shows their messages instead of submitting while one fails. Each copy of a component withForm(bind: …)has its own form, where all its copies shared one. - A bound
CheckboxorRadiowith its ownon changewrites its state first. The binding's write used to be lost, so a handler that wrote the state itself now writes it a second time, and one that toggles it (agreed = !agreed) undoes the click: take that write out. ASwitch'son change, which never ran, now runs. - Text that reads state follows it. Control labels, a
Table'scaption:, tab titles, tooltip text, a modal'stitle:, a menu's trigger, anAvatar, aSkeleton's sizes and anIcon's positional name kept the value they were drawn with; they now change with it. ACheckbox(label: t("…"))changes language withsetLocale. - An
Avatarwhosesrc:is a run-timedata:orblob:address gets an emptysrc, as any othersrc:does. - Built-ins write what they are given.
role:,tabindex:,title:,hidden:,aria-*,data-*andonhandlers on aVirtualList,Splitter,Tabs,Sidebar,Breadcrumb,Slider,DatePicker,FileUpload, the layers and the rest now reach their element, where some were dropped.label:on aVirtualList,SplitterorCarouselis written as itsaria-label, not as text in it.disabled: trueon aSlider,DatePickerorFileUploaddisables it. ASidebar'sid:is its id. Pre-rendered HTML andwf testsnapshots carry these too: look at the difference and runwf test --update.
Layers and keys
- The Escape that closes an open
ModalorDialogstays there: a page'son key("Escape")no longer runs for it. - An anchored layer hides with its anchor when the anchor scrolls out of view, and stays open. Style it through
[data-anchor-hidden]if you need to. - A modal's Escape and title. Over an open popover, the first Escape closes the modal and the next closes the popover. A press inside the modal no longer closes the popover beneath it. In the pre-rendered page, a modal's title is its heading. A tooltip under the pointer lets Escape go on to the page.
Language, state and stores
setLocaleis remembered. The choice is kept in the reader'slocalStorageunderwf:locale, and the next page opens in it; a?lang=address still wins. Apersiststore kept for the same purpose still works beside it.- Stores: a store's derived values keep following their state after the first page that read the store has gone, and one that reads a
derivedwritten below it follows it. The built script declares a store after the stores ituses. - A local of a member's name is the action's own. A store action that wrote a member through a
letof the same name now writes the local. data-x: truepassed through a component is"true", where it was"", so a selector on[data-x=""]stops matching.Portalis a built-in's name: a project's own component or store calledPortalis reported.- Markdown reads backslash escapes. A text with
\*,\_,\#,\[and the like now shows the character alone, and the character takes no part in emphasis or a link;\\is one backslash. A backslash at the end of a paragraph's last line is shown, where it was dropped. A link or picture whose address has a scheme a page refuses (javascript:,data:) is drawn as its words. - Fewer warnings and errors: an
Iconnaming one of the 23 new icons draws it instead of warningV08;on auxclick,on focusinandon focusoutno longer warnV09;on blurandon focusoutside an element compile, where they were an error; and() => valuefits a function of no arguments, where it wasT01.
Security headers
- A site that frames its own page, with a
Framewhosesrc:is a site-relative string ("/preview/","/embed/{id}"), is servedX-Frame-Options: SAMEORIGINandframe-ancestors 'self'. One whose same-site address comes from a variable is still servedDENY, so the browser still refuses it. Write the address as a string, such as"/embed/{id}".
Pre-rendered pages and tests
- Pre-rendered HTML matches the live page. A
MenuorDropdownis its button and a hidden list, so its entries no longer show before the script runs, and a menu that state opens is its list alone. ACheckbox,RadioorSwitchhas its<input>, with the control'sid:on it. A part written with flags carries their classes. AColumnwith a literalspan:carrieswf-col--N.disabled,requiredandcontrolsare left off when false, or when the build cannot know them. wf testsnapshots change where they hold aMenu, aDropdown, aColumnwith aspan:, akeyLabel, a count in a locale with more plural forms than English, or adisabled:,required:orcontrols:that is false: look at the difference and runwf test --update. Anexpectfor aMenu'slabel:text no longer finds it (it is anaria-label), and one for itstrigger:does.expectreads'as an apostrophe, and in a test that acts compares with white space collapsed. Aclickmay now find a tab, a menu item or a radio button it used to miss.- Tests read as a reader does. An
expectthat counted on a space between two elements that touch ("live : …") now reads them touching. A test run in a browser has the project's own CSS, so CSS that hides or changes text changes what the test sees, and a stylesheet naming a file not inpublic/fails it. Snapshots losedata-*attributes that werefalse, and gain a call'sdata-*,aria-*,idandclass:on a component's root. Runwf test --updateafter looking at the difference.
Windows and tools built on the compiler
- On Windows, type
webfluent(orwf.exe) wherever this guide sayswf. Each earlier.msihad anUpgradeCodeof its own, so the new one cannot replace it: uninstall the old one from Apps, or both stay installed and onPATH. - A tool built on the compiler adds the new fields where it writes a struct literal:
doconStateDecl,DerivedDeclandActionDecl,frames_itselfonBuildConfig,only_routeonBuildOptionsandpages_deferredonBuildReport. It adds aLength::Mix(..)arm where it matchespaged::style::Length, and passes a locale totesting::render_testas its fourth argument.print::statementtext for a documented member starts at its///, so replace fromprint::written_start.check_project_viastarts threads, and calls aProject'sfile_ofandsource_ofup front.
5.9
5.9 holds a few things to what this guide already said. Your project may notice them:
- A comma between two style declarations is an error (
E002).style { width: {w}px, flex: none }compiled to one declaration whose value was the rest of the line, so the browser dropped both. Write each declaration on its own line, or separate them with;. A comma inside a value (font-family: a, b) is untouched. - A store's
persist … key:is kept. It was dropped, so the value was kept under no key; now it follows the key, as a page's does. What is already stored is found under the same names. - A refined type's bounds are checked as the reader types where a
validateblock guards the state:Number(0..10)no longer takes 10, andDate(after: …)andbefore:are held. A field that accepted its open end now says Too large. Card(animate: .Drop)plays a project's own animation on an element that stands still. It did nothing before, so a page may now move where it did not.- A count of exactly 0 shows
key.zerowherever the translation file has one, in any language, and the pre-rendered page picks each count's form by the default locale's rules rather than English's. Azeromessage that never showed now does. - A site whose default locale is right to left is written
<html lang="ar" dir="rtl">from the first paint.meta.langnames a region of the default locale's language, and is otherwise the default locale. - New warnings:
A17(aFramewith no title) andV12(a long list that is not windowed).wf checknames each with its fix.
5.8, 5.7 and 5.6.x
Nothing to change.
- 5.8: a build may now warn
X06on astatewhose first value reads a live one, such asnow. Making itderivedis the fix. A function written only to get a script's value onto a page can go back to being the value. - 5.7: what a page did to live through a refresh can go — a sheet or a form kept outside the
matchwith a snapshot of the data, or aderivedcopy held so the arm would not draw again. A page that wants a spinner on every refresh shows one forname.refreshing. A hand-writtenWF.matcharm is handed its value as before, and an accessor of it as a second argument;WF.eachkeeps a keyed item's nodes under a new value withlive: true, which is what a compiledfor … byasks for. - 5.6.2: a wrapper written only to keep a nested branch apart — a
Stackstyleddisplay: contentsaround a tab'smatch, or a branch flattened into oneif letover aderivedvalue — can go. - 5.6.1: a
derivedvalue written only to make a resource's label live can go back into the label.
5.6
5.6 refuses a name the language already has as a program's own (E118): a state env, a loop's t, a persist theme, an action named update. Each compiled before, and read the language's value where the program meant its own — a page's state env showed [object Object].
Run wf check. The message names the declaration and suggests a name of your own; renaming it and its reads is the whole change. The usual renames:
| Was | Rename to |
|---|---|
|
a loop's or a lambda's |
|
|
|
|
|
|
|
|
a route parameter or |
|
|
an action named |
|
5.5
A value an OpenAPI specification marks as nullable is now T?, so a read that ignored null — Text(e.reason.toUpperCase()) — is T04 where it compiled before. Use ?., ?? or if let to say what to do when it is null. A response field with a format is now a DateTime, a Url and so on, and a String assigned to one is T01.
5.0
5.0 makes the compiler refuse much more of what used to compile and then fail in the browser. A project that built under 4.x may stop on errors it always had. Start with a check, which writes nothing:
$ wf check
Every finding names its code, its place and what to do. wf explain CODE prints the code's entry in Diagnostics. Where the fix is known, your editor offers it as a quick fix, and wf check --format json lists it as edits.
New errors. Each is a program that cannot work as written:
- Types (
T): a field, member or method that does not exist; a value of the wrong type; a value that may benullread as if it were not; amatchthat misses a case; arithmetic on what is not a number; a comparison that is always the same; anawaitwhere it cannot run; a name nothing declares. - Writing what cannot change (
X01): aconst, aderivedvalue, a prop, a route parameter, a loop variable. - Components (
C): a required prop left out, a prop the component does not declare (C02), a part outside its owner. - Routes (
R): a link to a path no page matches (R01), a:paramwith no page parameter, anappwith noRouteror with two; two pages on one path (S04). - Forms (
F):bind:to something that cannot be written, or to a state the control cannot hold; avalidateno control can satisfy. - Reactivity (
X): an effect that writes what it reads every run, aderivedvalue that calls an action,useof a store nothing declares. - Data and translations (
D,I): a persisted value storage cannot keep; at("key")no translation has, a placeholder the call does not pass, a locale the project does not list. - Literals and styles: a date that does not exist, money with too many decimals, a key combination no keyboard sends, a
$tokenthe theme does not declare. - The security policy: a page's
head { script(src: …) }from an origin the config does not declare (E902).
Lower what you cannot fix today. "lints": { "R01": "warn" } in the config lowers a code or a family. An error may be lowered only when it ships no broken page: R01, C02, S04, I01, I02, I04. To accept one finding on one line, write // wf-allow(CODE) (Diagnostics).
What the compiler now writes for you instead of reporting:
- A change inside a state's value —
form.name = v,items[i].done = v,items.sort()— compiles to the state given an updated copy, so what reads it repaints andpersistkeeps it. - A value spliced into an address —
to:,navigate(), a request's address — is encoded where it stands for a value. - A
matchexpression that covers every case of an enum needs noelse.
Behaviour that changed:
wf serveanswers a missing fetch with a 404. A request that is not a page navigation, for a file the build did not write, used to get the single-page shell — a page of HTML handed toJSON.parse. It is a404now, underwf verifyandwf testtoo, andwf serveprints a line for each. Point the page at a server that has the API, or put a file inpublic/.- An empty path parameter is not sent.
Backend.user(id: "")withat "users/:id"used to requestusers/, the whole collection. It now ends as.aborted, and a resource over it staysloading. - One list item that throws no longer blanks the list: the rest draws, and under
wf servethe item says what it threw. - An effect that never settles is stopped after 100 runs, instead of overflowing the stack.
- Each build keeps what its persisted values start as in
.wf-cache/, so the next build can warn about a shape that changed (D04), andwf verify --returning-visitorcan load your pages as a returning reader. Keep.wf-cache/between CI runs if you can.
New in 5.0: wf check, wf explain, --format json|sarif|github and --deny-warnings on wf build and wf check, quick fixes in the editor, persist … { key: id } for one stored value per instance, and wf verify visiting :param routes. Command line describes each.
4.2
external is gone. Run wf migrate. It turns a remote module into a meta.scripts entry, a local module into a plain script under src/ with its signatures as JSDoc, and an external element call into Element("tag", …). A call into a remote module that external typed is untyped afterwards (Json since 7.0).
Every .js file under src/ now ships, linked on every page before the compiled code. wf migrate lists the ones it finds; move any that are not meant for the browser out of src/.
New in 4.2:
- Your own JavaScript: a plain
.jsfile undersrc/, its top-level functions in scope by name, typed by its JSDoc (JavaScript interop). meta.scriptsloads a library from a CDN, imports a module withas:, and names itsglobals.mount:,update:,cleanup:on any element, and awf:renderevent for a script that finds elements itself.Element("tag-name", …)places any custom element.class:takes a map and a list:{ "is-done": done },["card", tone, if open { "is-open" }]. Anifwith noelseisnullwhen its condition fails (Styling).V04warns about aclass:that borrows one of the built-ins'wf-classes.
Fixed in 4.2: what an if branch, a match arm, a list item or a slot fill made — a timer, an effect, a Host's cleanup — now goes when its page does. A route change used to leave it running.
4.1
Nothing to change in your code. New in 4.1:
- Offline: name
offlinein the config for a service worker, writes kept for later, and an update flow (Offline). - Peers:
peer link = rtc(signal: …), a WebRTC data channel to another page (Realtime). envfrom a.envfile and the shell, on top of the config (Environments).- Unknown config keys are reported, with the key they probably meant.
- Pagination:
paginate: .page,.items,.loadMore(),.hasMore. ?lang=opens a page in that locale, as thehreflangalternates promise.class-exported libraries work throughexternal: a class is constructed when called.- Every standard DOM event is accepted in
on ….
Fixed in 4.1, and worth knowing because they could have affected you:
Caution
A private env value no longer reaches the bundle. 4.0 refused a page that read a private name, but still wrote the whole env map into app.js. If you deployed 4.0 or 4.0.1 with a secret in env, rotate it.
- An action's parameters are its own:
action move(by: Number)readbyas a signal and threw. head { }tags may read a page'sderivedvalues.- A resource's
state,dataanderror, and a socket'smessages, show their values in text. navigatorandlocationcompile as the browser's.- Two declarations on one line —
theme T { color-primary: #0F766E radius-md: 14px }— are two, not one. S04reports two pages on one route;A12counts anh1in each branch of anifas one.
4.0
4.0 changed what the compiler allows. wf migrate handles the mechanical part and names every place that needs a decision. Preview what it would change, then apply it:
$ wf migrate --check
$ wf migrate
envis public or private. A page may only read a name beginningPUBLIC_or listed inpublic_env. The migration adds every name your pages already read topublic_envand prints the list. Read the list: public means anyone who opens the site can read the value.- An
on*attribute is an error (onclick: "…"); writeon click { }. - A URL a browser would run is refused —
javascript:,data:,vbscript:,blob:,file:inhref:,src:,to:,poster:ornavigate(). - Stores are built on first read, not at boot. A store whose set-up must run anyway takes
eager: true. - A
persistvalue follows other tabs.sync: falseopts out. WF.storeandWF.hostwere renamed in the runtime's functions.- Layouts stay as written: a
Rowno longer turns into a column on a narrow screen by itself. The migration adds.stacksto keep the old behaviour.
3.x
WebFluent 3 introduced the grammar this guide describes: lowercase declarations, one positional argument, flags after a dot, on click { } handlers, and style { } blocks of CSS. A 3.x project moves forward with the 4.0 notes above.
From WebFluent 2
wf build refuses a WebFluent 2 file (Page Home (path: "/") { … }) and points you to the migration. wf migrate rewrites every .wf under src/ into the current grammar. It is a change of spelling only: the migrated project builds to what it built before. wf migrate --wfx writes the result in the indented layout.