survivejs/webpack

Feel free to ask questions related to the book content or webpack here. I'll get to them eventually. Stack Overflow or Reactiflux is likely faster for general questions, though.

Anthony DeGennaro

@okanthony

@bebraw here's the branch and here's the require.context() implementation

Juho Vepsäläinen

@bebraw

cool, i'll try to check today after getting the urgent things done :+1:

Juho Vepsäläinen

@bebraw

@okanthony would it be cleaner to run the mocha tests in browser directly? reference: https://stackoverflow.com/a/42858362/228885

maybe it's worth checking what codesandbox is doing. i am missing the big picture a little bit

Anthony DeGennaro

@okanthony

Hmm I initially tried running mocha in the browser but wasn't able to filter the tests without resetting the state of the app. I'll take a look into codesandbox and see if there's anything I can use, I appreciate the help!

Logan Valentine

@krandom

Hi guys! How would I add eg "import { react-redux } " to globalInclude?

Juho Vepsäläinen

@bebraw

@okanthony it's likely worth looking into mocha apis. maybe they have something specific for this? just for reference, i wrote a browser oriented testing lib many moons ago (https://github.com/bebraw/bunit.js)

@krandom what's the use case? can you give some context?

Anthony DeGennaro

@okanthony

@bebraw oh nice, I’ll look into both, thanks!

Anthony DeGennaro

@okanthony

the mocha api has a bunch of methods that would handle what I'm trying to do, but I'm guessing I wouldn't be able to use the mocha-loader in conjunction with them?

Juho Vepsäläinen

@bebraw

@okanthony that's what i mean - i would look into using mocha without the loader

then you have more flexibility at least

Nikos

@QuantumInformation

thx for lunch today!

Juho Vepsäläinen

@bebraw

:+1:

George E. Papadakis

@phaistonian

hey @bebraw :)

Juho Vepsäläinen

@bebraw

hey

George E. Papadakis

@phaistonian

hey :)

Juho Vepsäläinen

@bebraw

feel free to post your question here, i'll get back to it after i'm done with the day's work

George E. Papadakis

@phaistonian

Thanks :)

So, say I have a SVG asset and I want to load it using the react-svg-loader. But I only want this to the case when directly importing it, i.e import "myLogo.svg" not when the asset is referenced in, say, <img src="myLogo.sg" /> in which case I need the file-loader to work

Juho Vepsäläinen

@bebraw

@phaistonian i can see two main ways 1. more specific config (include or so) 2. import "react-svg-loader!myLogo.svg" but that's not particularly nice. the loader chapter of the book provides more ideas

George E. Papadakis

@phaistonian

Yes, those are the way I can do i - the ones that also came to mind first

But this is a bit uggly

I was trying to figure out if using issuer in a certain way would do it

But it's also probably a dead-end

Juho Vepsäläinen

@bebraw

i would go with a config based solution. note that include accepts a function as well so that could be easier to dev and understand

George E. Papadakis

@phaistonian

yes, however include is path/file based

Can't limit it to, say, where it' s used

Juho Vepsäläinen

@bebraw

ok, maybe you can figure out a rule based on which to match then

George E. Papadakis

@phaistonian

Unfortunately, the same assets (in terms of paths) are referenced both as direct import but also as src="..."

One - hacky - solution would have been to be able to do src="!file-loader!..."

but we can't

George E. Papadakis

@phaistonian

(Or you can - solved it :)

Andrea Chiumenti

@kiuma

hello, I'm having some problems with eslint-loader and imports from local file system:

I've the loader with this test and exclude

 test: /\.js$/,
exclude: /node_modules/,

I've imported a lib from local fs
but then the system complains with the transpiled files of the library : /home/kiuma/projects/ui-libs/core/utils/webComponent.js

Why loaders are not ignoring my lib ?

Juho Vepsäläinen

@bebraw

@kiuma i think your exclude doesn't cover imports from outside of the directory itself. likely you have to extend the definition or use an include instead as that would avoid the problem

in practice, i've found it better to use eslint in combination with lint-staged as it's more efficient

the point is that the tool will only lint the files staged to git commit and as it turns out this is enough

Andrea Chiumenti

@kiuma

hello , I'm haveing an issu with symlink. my wp config file creates a symlink in src folder but it seems wp try to search deps in a remote node_mudules and not the application

How should I manage symlinks ?

Juho Vepsäläinen

@bebraw

i don't know the exact setup but symlinks but i know you could use something like https://verdaccio.org (npm proxy). it's possible to run it locally. what you can do is to publish there locally and then npm install as usual. that avoids the issue with symlinks

Andrea Chiumenti

@kiuma

Hi @bebraw finally I solved the issue setting resolve: { symlinks: false } this way the local path i used instead of the linked one and node_modules works as I expected

Juho Vepsäläinen

@bebraw

@kiuma ah, cool to hear :+1:

Juho Vepsäläinen

@bebraw

@kiuma i found something potentially useful for you, https://github.com/whitecolor/yalc

George E. Papadakis

@phaistonian

Hey @bebraw - still arounD?:)

Juho Vepsäläinen

@bebraw

sure, i check this daily

i did a small side project, https://bebraw.github.io/sidewind/

i still have to finalize the internal API so it's easy to consume and extend but apart from that it's in a usable state

there's no component model but i would use templating or so for that

Where communities thrive

People

Repo info

Activity