developit / microbundle Goto Github PK

I'm trying to compile a quite simple app.

// @flow
// index.js
import { h, render } from 'preact';
import App from './components/App.js';

const appElement = document.querySelector('#app');

appElement && render(<App />, appElement);

// components/App.js
// @flow
import { h } from 'preact';
import styled from 'preact-emotion';

const Container = styled('main')`
  color: red;
`;

export default function App() {
  return <Container>Red</Container>;
}

But I get:

Error: 'default' is not exported by ../node_modules/prop-types/index.js

This is my babelrc:

{
  "plugins": [["transform-react-jsx", { "pragma": "h" }], "emotion"]
}

It looks like the error happens when I import preact-emotion

Hello,

I trying to generate an UMD bundle including all the dependencies necessary. This is the code:
https://github.com/microlinkhq/microlinkjs/blob/master/packages/microlinkjs/src/index.js

I'm running the following command:

❯ NODE_ENV=production npx microbundle build --target browser --entry lib/index.js --format es,cjs --inline all
Build output to lib:
      1.54 kB: index.js
      1.54 kB: index.m.js

But the filesize is too small, because it doesn't include all the code dependencies.

I'm trying with external:none or inline:all but looks like the code doesn't support it
https://github.com/developit/microbundle/blob/master/src/index.js#L152

How can I do that using microbundle?

When run npm run build, I got this error:

Error: Error transforming bundle with 'uglify' plugin: Unexpected token: name (Screen$1)

cc: @developit I think there is a problem with rollup-plugin-uglify

When I try to build my module this was comes up.

$ yarn microbundle
yarn run v1.1.0
$ microbundle build
Using named and default exports together. Consumers of your bundle will have to use jaysn['default'] to access
the default export, which may not be what you want. Use `exports: 'named'` to disable this warning
(node:4720) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Error transforming bundle with 'uglify' plugin: Unexpected token: name (StructError)
(node:4720) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
Using named and default exports together. Consumers of your bundle will have to use jaysn['default'] to access
the default export, which may not be what you want. Use `exports: 'named'` to disable this warning
(node:4720) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Error transforming bundle with 'uglify' plugin: Unexpected token: name (StructError)
Error: Error transforming bundle with 'uglify' plugin: Unexpected token: name (StructError)
Done in 13.40s.

This repo I was try to build https://github.com/lowsprofile/jaysn

This is my package.json

{
  "name": "jaysn",
  "version": "0.1.3",
  "description": "Lightweight JSON database for Node, Hybrid, and browser.",
  "homepage": "https://lowsprofile.github.io/jaysn/",
  "repository": "lowsprofile/jaysn",
  "author": "Eries Trisnadi <[email protected]> (https://eries.id)",
  "license": "MIT",
  "keywords": [],
  "main": "dist/jaysn.js",
  "module": "dist/jaysn.es.js",
  "eslintConfig": {
    "parser": "babel-eslint",
    "extends": "airbnb-base"
  },
  "files": [
    "dist",
    "README.md",
    "LICENSE"
  ],
  "source": [
    "src/Jaysn.js"
  ],
  "dependencies": {
    "immutable": "~4.0.0-rc.9",
    "path": "^0.12.7",
    "superstruct": "^0.4.5"
  },
  "devDependencies": {
    "babel-cli": "^6.26.0",
    "babel-eslint": "^8.0.2",
    "babel-plugin-transform-es2015-destructuring": "^6.23.0",
    "babel-plugin-transform-es2015-function-name": "^6.24.1",
    "babel-plugin-transform-es2015-parameters": "^6.24.1",
    "babel-preset-es2015": "6.24.1",
    "babel-preset-es2015-rollup": "^3.0.0",
    "babel-preset-stage-1": "^6.24.1",
    "babel-register": "^6.26.0",
    "chai": "^4.1.2",
    "coveralls": "^3.0.0",
    "eslint": "^4.12.0",
    "eslint-config-airbnb-base": "^12.1.0",
    "eslint-config-prettier": "^2.9.0",
    "eslint-plugin-import": "^2.8.0",
    "eslint-plugin-prettier": "^2.4.0",
    "microbundle": "^0.2.4",
    "mocha": "^4.0.1",
    "mustache": "^2.3.0",
    "npm-run-all": "^4.1.2",
    "nyc": "^11.3.0",
    "prettier": "1.9.2",
    "rollup": "^0.52.0",
    "rollup-plugin-babel": "^3.0.2",
    "rollup-plugin-buble": "^0.18.0",
    "rollup-plugin-commonjs": "^8.2.6",
    "rollup-plugin-json": "^2.3.0",
    "rollup-plugin-node-resolve": "^3.0.0",
    "rollup-plugin-strip-banner": "^0.2.0",
    "rollup-plugin-uglify": "^2.0.1",
    "shx": "^0.2.2",
    "sinon": "^4.1.2",
    "uglify-es": "^3.2.0",
    "uglify-save-license": "^0.4.1"
  },
  "scripts": {
    "build": "run-s format build:*",
    "build:dist": "run-s clean:dist bundle format:dist",
    "build:docs": "run-s clean:docs mustache",
    "bundle": "run-s bundle:*",
    "bundle:cjs": "run-s \"rollup -c tools/build-cjs.js\"",
    "bundle:es": "run-s \"rollup -c tools/build-es.js\"",
    "format": "run-s \"lint --fix\"",
    "format:dist": "prettier --write \"dist/**/{jaysn.es.js,jaysn.js}\"",
    "clean:dist": "run-s \"rm -rf dist\"",
    "clean:docs": "run-s \"rm -rf docs\" \"mkdir docs\"",
    "coverage": "nyc report --reporter=text-lcov | coveralls",
    "lint": "eslint src test tools",
    "microbundle": "microbundle build",
    "mkdir": "shx mkdir",
    "mustache": "node tools/build-docs && shx cp -r resources/css docs && mustache -p resources/partials/menu.mustache -p resources/partials/content.mustache resources/docs.json resources/docs.mustache > docs/index.html",
    "prepublish": "run-s build",
    "rm": "shx rm",
    "rollup": "rollup",
    "test": "run-s -l lint \"test:mocha {@}\" test:cover --",
    "test:mocha": "mocha --require babel-register",
    "test:cover": "nyc --require babel-register mocha --timeout=3000"
  }
}

IMHO it makes debugging harder, its not easy to look into source code of libraries in node_modules (built by microbundle) nor it is easy to debug microbundle itself because its built by itself with --compress true (default).

I guess the question is what is a primary goal & target of this tool? If producing micro libraries then I think files should be left unminified by default, minifying can be done later by subsequent tools - bundlers etc.

Hi,
bublé supports some transform out of the box : https://buble.surge.sh/guide/#command-line-options
maybe we could add an options to let the user add transforms he needs without adding babel to the mix.

With a module importing date-fns, microbundle throws "TypeError: Cannot read property 'code' of undefined". See this reduced test case.

I've recently built a Vue.js component for lazy loading images and wanted to use microbundle for its setup, but couldn't make it work.

What's required to have Vue.js support?

This tool need a test setup - for obvious reasons. I'd like to work on some features, but I'm totally not confident about making changes.

I'd like to work on this, but I'd like to establish what kind of tests should be written. I feel that snapshot testing might be a good for this - as primary testing solution. Additionally we could write some additional manual tests, but for a tool such as this such tests are often not obvious.

Beside setting up a testing infrastructure I'd appreciate coming up with good testing scenarios (especially for more convoluted options/combination of options etc) that I could not come up with without examinating the source code carefully.

Probably unpopular opinion, but I don't always want sourcemaps to be produced. This is especially true when #66 takes shape.

This isn't a massive pain point or anything, so feel free to disregard~!

Hi, i wonder if it's possible to use JSX in the source code.
This is a test repo : https://github.com/wcastand/test-microbundle
I have a small repo to test it out and right now i get an error from nodent :

▲ test-microbundle at master ✔ yarn build
yarn run v1.3.2
$ microbundle --jsx
SyntaxError: Unexpected token (4:2) /Users/willoo/Documents/Projects/test-microbundle/src/index.js (nodent)
  <div>
--^
✨  Done in 0.50s.

In the source code you have an options for jsx in buble options.jsx but nodent is before buble.

Looks like buble supports it, as long as you pass an option for objectAssign: 'Object.assign' but in practice it doesn't seem to be working.

My code:

import { h } from 'preact'

export default ({ title, ...rest }) => (
  <div {...rest} className={`${rest.className}`} />
)

Output:

SyntaxError: Unexpected token (3:25) /some/path/page.js (nodent)
export default ({ title, ...rest }) => (
-------------------------^

Fooling around: https://github.com/probablyup/markdown-to-jsx/tree/microbundle

Doesn't seem to be honoring my babelrc and it's blowing up on some ES6+ syntax:

yarn run v1.3.2
$ microbundle build
SyntaxError: Unexpected token (553:12) /Users/bear/code/markdown/index.js (nodent)
            ...overrideProps,
------------^
✨  Done in 0.75s.

The title probably says everything, but my problem was that I tried microbundle in a local package without a name field in the package.json file. This currently throws an internal error when replace is called on undefined (pkg.name).

I'd be happy to open a PR to fix this if you'd like, but I wasn't sure how you'd want to handle it (warn and exit? something else?).

Anyway, thanks for building this, it looks like a very useful tool!

Hi,

Maybe I'm doing something wrong, but I'm writing a github-like markdown editor and I got into this issue.

TypeError: Object prototype may only be an Object or null: undefined

It happens if I try to include a 3rd party package. (using yarn link in my main folder and yarn link @webscopeio/react-markdown-editor in demo folder)
I'm sorry if I misunderstood something, I'm pretty new to bundling OSS React components. It's my first attempt.

Do you have any idea what am I doing wrong? I've been trying for hours :/

Code is available here https://github.com/webscopeio/react-markdown-editor

Hey,

I'm intereted in know how to define correctly each bundle at package.json.

For example, I know cjs bundle is the property main.

What happens with the rest? Could be a great resource to put into the readme 🙂

When trying to install globaly via sudo npm i -g microbundle I get this error

Error: EACCES: permission denied, open '/usr/local/lib/node_modules/microbundle/node_modules/nodent-runtime/dist/index.js'

Is it an issue with nodent-runtime or microbundle?

Great to see the progress on typescript integration !

However the current version uses rollup-plugin-typescript which uses Typescript 1.8 which is very old.

I think switching to rollup-plugin-typescript2 should bring better defaults. In addition I think this should help with #58

Recommend adding uglify passes: 3 compress option to:

for smaller bundle sizes.

Example:

$ bin/uglifyjs -V
uglify-es 3.3.9

$ cat example.js 
var o = {
    foo: 1,
    bar: 2,
    square: x => x * x,
    cube: x => x * x * x,
};
console.log(o.foo, o.cube(3));

$ cat example.js | bin/uglifyjs --toplevel -mc
var o=1,l=o=>o*o*o;console.log(o,l(3));

$ cat example.js | bin/uglifyjs --toplevel -mc passes=2
console.log(1,(o=>o*o*o)(3));

$ cat example.js | bin/uglifyjs --toplevel -mc passes=3
console.log(1,27);

Love the simplicity!

Do you have any plans to add Typescript support at some point?

maybe something like

microbundle --ts
// or
microbundle --transpile=typescript

Hello,

Im importin external npm package.
When im using const parse = require('form-parse'); my file size is much lower than using import parse from 'form-parse';

require =>
Wrote 884 B: index.umd.js
Wrote 818 B: index.js
Wrote 821 B: index.m.js

import =>
Wrote 2.6 kB: index.js
Wrote 2.65 kB: index.umd.js
Wrote 2.6 kB: index.m.js

Im writing a module for babel that converts to browser script.

Why size is so different and wich one should i use ?

Hey!

I'm getting the error "Error: Unexpected token" with this code:

class Base {}
export default () => {
  return class extends Base {};
};

If I change it to:

class Base {}
export default () => {
  class R extends Base {}
  return R;
};

...it then works. It seems the class extends run together is what's causing the problem. My intuition tells me that maybe this issue is down the tooling stack in Bublé or Nodent, possibly, but I didn't find any errors when running through them separately. I didn't have time to check Rollup or the Uglify plugin for it yet due to time constraints.

I could have missed something somewhere, though. Any help or guidance on this would be appreciated.

It looks like 0.4.4 did break some defaults for index.ts
Get Could not find file error

$ pwd                                                                                                                                                    
/Users/me/Dev/temp/sample
$ microbundle -v                                                                                                                                         
microbundle, 0.4.4
$ microbundle                                                                                                                                            
Error: Could not find file: '/Users/me/Dev/temp/sample/src/index.ts'.
$ ./node_modules/.bin/microbundle -v                                                                                                                     
microbundle, 0.4.3
$ ./node_modules/.bin/microbundle                                                                                                                        
Build output to dist:
      1.86 kB: sample.js
      1.86 kB: sample.esm.js
      1.92 kB: sample.umd.js

{
  "name": "sample",
  "version": "0.0.1",
  "main": "dist/sample.js",
  "jsnext:main": "dist/sample.esm.js",
  "module": "dist/sample.esm.js",
  "dev:main": "dist/sample.dev.js",
  "minified:main": "dist/sample.min.js",
  "devDependencies": {
    "microbundle": "0.4.3"
  }
}

For adding strict mode we need to add --strict=true flag according the docs.
Expected result: use strict is inserted in the bundle.
Actual result: use strict is not inserted in the bundle.

Reasons: looks like in yargs https://github.com/yargs/yargs/blob/master/docs/api.md#optionkey-opt flag default value of the type flag is 'string' , so your check (options.strict===true) always return false

Possible solution: add type: "boolean", in yargs.option('strict', { // ...})
version: 0.2.4

It's just a request to evaluate if exports: 'auto' is still today the best solution. I understand its nice to use require('lib') instead of require('lib').default, but imho the BIG problem with having this auto mode by default is that whenever a user adds a named export from his/her library it is automatically a breaking change and one that might easily slip released as patch/minor because its really simple to miss that.

I'll make piece with either decision, just wanted to raise a concern about this.

I've filled this issue at rollup - rollup/rollup#1881 , but whatever they decide does not have to be the same for microbundle, hence "duplicated" issues.

Does this support creating a react component library and importing a global stylesheet like import tailwindcss/dist/tailwind.min.css?

How can I specify multiple formats? e.g. cjs and es. I thought I would so something like this:

microbundle src/*.js --format 'cjs,es'

But it doesn't work. I get this error:

$ microbundle src/*.js --formats 'cjs, es'
Error: Invalid format: cjs, es - valid options are amd, cjs, es, iife, umd

Any ideas?

Having this implemented would resolve this issue.

The idea is that we need to output private package.json files to support appropriate es/cjs resolving, I believe that @kentcdodds got it "right" here. Although you might prefer having some convention for creating additional "entries" over additional config flag.

I will work on implementing this, hopefully some time soon~

I tried the new TypeScript support in version 0.4.0 and it is awesome! Thank you!

However, I have a question regarding the declaration files. Shouldn't they be emitted as well?

tsconfig.json

{
  "compilerOptions": {
    "target": "ES2015",
    "module": "commonjs",
    "declaration": true,
    "outDir": "dist"
  },
  "include": ["src/**/*"],
  "exclude": ["node_modules", "**/*-spec.ts"]
}

and the output in the dist folder contains all files (index.js, index.m.js, index.umd.js and respective map files) except index.d.ts. Any idea?

Hello,

I'm interested in add support for include all the dependencies in the final bundle.

This conversation started on Twitter:
https://twitter.com/_developit/status/940937797589983235

After check the code, I only seeing a way to excluding, not including:

According your docs dev mode should be run via watch command. In this case I expect that bundle should not have minification (--compress=false). It's more conveniently to debug code by default.

Is it possible to change it to mentioned flag?

I am trying to include a library at the top of my file via import 'wicg-inert and I get the following error? Is this not possible via microbundle?

That slant tape is driving me insane 😅
Mind if I fix?

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

Heya! 🎉

First of all, yea.. it is not for apps (i think?), but it is possible to some extent. So we may include rollup-plugin-serve or *-server, and rollup-plugin-livereload.

Currently you can use watch and in another terminal to use some static serving tool, like wrapping micro(-dev) or directly us serve / budo. Budo is good enough and has livereload, but it bundles one more time unneccesary (cuz the trick is to budo dist/bundle.cjs.js --live). Also, you need to handle cleaning of dist and creating a index.html. So the scripts are something like that

{
  "scripts": {
    "index": "echo '<script src=\"./index.js\"></script>' > dist/index.html",
    "clean": "rm -rf dist",
    "predev": "yarn clean && mkdir dist && yarn index",
    "dev": "microbundle watch -f cjs --inline none",
    "server": "budo dist/index.js --live --port 5000"
  }
}

It looks like an option is explicitly set to make only es module dependencies included. In practice, it assumes any non-es-module dependency is "external" and doesn't bundle it. Just curious about the rationale behind this choice? It really limits the utility of this tool, as most libraries still don't export an es module version at this point.

https://github.com/developit/microbundle/blob/master/src/index.js#L195

After upgrading to 3.0.0 i can't run microbundle with npm scripts.

/bin/sh: microbundle: command not found

I happened to hear about microbundle a day or so ago so I decided to try it on a tiny library I was hacking on. The output seems really weird, though:

function t(t){return new Proxy(t,{get:function(t,r){return r in t?t[r]:e.lookup(r)}})}var r=function(){this.reset()};r.prototype.register=function(t,r){this._registry.set(t,r)},r.prototype.lookup=function(t){return this._registry.get(t)},r.prototype.reset=function(){this._registry=new Map};var e=new r,n=function(){return t(this)};n.extend=function(r){return function(r){function e(){return r.call(this),t(this)}return r&&(e.__proto__=r),e.prototype=Object.create(r&&r.prototype),e.prototype.constructor=e,e}(r)},exports.registry=e,exports.RegistryAccess=n;
//# sourceMappingURL=index.js.map
kup(prop);
        }
    });
}

var RegistryAccess = function RegistryAccess() {
    return registerForAccess(this);
};
RegistryAccess.extend = function (Klass) {
    return (function (Klass) {
        function anonymous() {
            Klass.call(this);
            return registerForAccess(this);
        }

        if ( Klass ) anonymous.__proto__ = Klass;
        anonymous.prototype = Object.create( Klass && Klass.prototype );
        anonymous.prototype.constructor = anonymous;

        return anonymous;
    }(Klass));
};

export { registry, RegistryAccess };
//# sourceMappingURL=index.js.map

That's the contents of the dist/index.js file that is output. It doesn't even seem like valid JS syntax after the first sourceMappingURL comment.

You can clone and try it yourself here:

https://github.com/alexlafroscia/service-locator

Here is demo with reproduce.
I'm build my library that depends on multiple packages, that i want to be bundled with my lib.

https://github.com/KatSick/microbundle-mlr-issue

You need to run:

yarn
yarn build

and see error:

(node:11685) UnhandledPromiseRejectionWarning: Error: 'Component' is not exported by node_modules/react/index.js
    at error (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:170:15)
    at Module.error (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:17170:9)
    at missingExport (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:16843:12)
    at Module.trace (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:17253:17)
    at ModuleScope.findVariable (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:14344:28)
    at Node.Identifier.bindNode (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:11993:40)
    at NodeBase.bind (/Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:11007:14)
    at /Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:11013:56
    at /Users/ochervak/Projects/Self/microbundle-mlr-issue/node_modules/rollup/dist/rollup.js:11027:66
    at Array.forEach (<anonymous>)

I have a structure very similar to lodash.

import module1 from 'project/module1'
import module1 from 'project/module2'
import module1 from 'project/module3'
...

My entry point looks like (index.js):

module.exports = {
    module1: require('./module1'),
    module2: require('./module2'),
}

Is it possible that microbundle creates a file for each module separately? Because I'm getting index.m.js and index.umd.js

.map file has empty sourse map
{"version":3,"file":"bundle.m.js","sources":[],"sourcesContent":[],"names":[],"mappings":";;;;;;;;;;;;;;;;;"}

used version 0.2.4

So apparently webpack will follow the module property of package.json files over the main entry. Since microbundle uses this property to point to the un-processed source file, webpack will pull the raw source file whenever you try to import a microbundled package, entirely defeating the point of processing the file in the first place.

I'm not entirely sure what the right fix is for this - ultimately, you likely want webpack to pull the xxx.m.js version which has been processed by babel but is still using es modules, but this is impossible without breaking microbundle's entry point.

I guess my gut would be to use a different property for microbundle's entry point - happy to PR to help fix this if you have any suggestions.

I'm unable to run the microbundle from master without getting the error above.

The last successful SHA is ff42a14 (just before the upgrade to [email protected])

Env:
macOS 10.13.2
node 8.9.4
npm 5.6.0

Repro:

git clone https://github.com/developit/dlv.git
cd dlv
npm i
npm i --save-dev developit/microbundle
npm run build

How can I define globals to avoid "....– treating it as an external dependency" msgs.

Nice work on microbundle!

I'm using microbundle via unistore, and I can't get the commands with glob work.

$ microbundle src/integrations/*.js -o x.js -f cjs
Error: ENOENT: no such file or directory, open 'C:\Users\srph\Code\oss\unistore\src\integrations\*.js'

I reckon this has something to do with the globbing. Have yet to investigate. Putting this up here in case someone else might be experiencing the same thing.

OS: Windows 10
TTY: Git Bash (mintty 2.7.3)

Edit: Turns out that npm run build of this project itself neither works.

$ npm i
> [email protected] install C:\Users\srph\Code\oss\microbundle\node_modules\nodent-runtime
> node build.js

## Built C:\Users\srph\Code\oss\microbundle\node_modules\nodent-runtime/dist/index.js

> [email protected] 

Hi there, I was super excited to find this project. Unfortunately, I can't get it working. I end up getting this error whenever I do anything:

$ npm run prepare
> [email protected] prepare /Users/aaronjensen/Source/react-multicast
> microbundle

Error: Plugin 'jsx' not found

Here's my repro repo: https://github.com/substantial/react-multicast (checkout branch repro)

Maybe I'm just doing something wrong?

☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.

Version 0.56.4 of rollup was just published.

This version is covered by your current version range and after updating it in your project the build failed.

rollup is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

Suppose I have

{
  "name": "@bebraw/schnitzel",
  "version": "0.0.0",
  "description": "",
  "main": "src",
  "scripts": {
    "build": "microbundle",
    "dev": "microbundle watch"
  },
  "keywords": [],
  "author": "",
  "license": "MIT",
  "devDependencies": {
    "microbundle": "^0.2.3"
  }
}

and src/index.js.

If I run npm run build, it generates src/@bebraw.

Is that expected?