flarum-webpack-config useExtensions option not working?

tooreht

I'm in the process of upgrading our extensions to beta.8. All went quite smoothly so far, I'm really impressed!
Now I'm working on the frontend. Converting the js code to webpack was a breeze. Now I try to override the view function of the TagsPage component. According to the README of flarum-webpack-config one can inject extension modules with the useExtensions option:

webpack.config.js

var config = require('flarum-webpack-config');

module.exports = config({
    useExtensions: ['flarum/tags']
});

forum.js

import { TagsPage } from '@flarum/tags/forum';

It compiles, but in the browser it throws a TypeError: _flarum_tags_forum__WEBPACK_IMPORTED_MODULE_4__ is undefined.

Does anyone know whats going wrong here?

Edit I found a dirty workaround:

const TagsPage = flarum.core.compat["tags/components/TagsPage"];

datitisev

tooreht That's not how you import things in Flarum. The correct import statement would be as follows:

import TagsPage from '@flarum/tags/components/TagsPage';

tooreht

datitisev Thx for your help. I also expected this to work, but it doesn't. At least not on my machine.
I have my extension configured as described above, upgraded all the node modules, but the import statement throws a

Module not found: Error: Can't resolve '@flarum/tags/components/TagsPage'

already at compile time running npm run dev. So I don't see another way than this dirty workaround atm.

datitisev

tooreht My apologies, the @ is not needed here. It should be flarum/tags/components/TagsPage.

tooreht

datitisev No worries, thank you, it works now! Did I get this right, this only works because of the exposure of the compat API, it has nothing to do with the useExtensions option, because flarum/tags doesn't have any exports in admin or forum?

datitisev

tooreht Honestly, not sure exactly how it works myself. However, I do know that only the code in admin/ and forum/ are loaded when in the admin and forum areas, respectively, so that can't be in the path.

You can have two imports that look the same but point to different files. For example, importing flarum/Application (or flarum/app) returns two different files depending if you are in the admin or forum areas.

The path after flarum/tags is just the path to the file.

Hope that helped 🙂.