GithubHelp home page GithubHelp logo

Comments (7)

stephenmathieson avatar stephenmathieson commented on May 1, 2024 2

@NicholasGWK thats what ive got too. pretty annoying...

screen shot 2016-05-06 at 09 05 06

from memory-fs.

stephenmathieson avatar stephenmathieson commented on May 1, 2024

any word on this?

from memory-fs.

engageft3 avatar engageft3 commented on May 1, 2024

Tried implementing @dapetcu21's solution and I'm still getting the same error:

            throw new MemoryFileSystemError(errors.code.EINVAL, path);
         ^
Error: invalid argument
    at pathToArray (node_modules\webpack-dev-middleware\node_modules\memory-fs\lib\MemoryFileSystem.js:44:10)
    at MemoryFileSystem.mkdirpSync (node_modules\webpack-dev-middleware\node_modules\memory-fs\lib\MemoryFileSystem.js:139:13)
    at MemoryFileSystem.(anonymous function) [as mkdirp] (node_modules\webpack-dev-middleware\node_modules\memory-fs\lib\MemoryFileSystem.js:279:34)
    at Compiler.<anonymous> (node_modules\webpack\lib\Compiler.js:229:25)
    at Compiler.applyPluginsAsync (node_modules\webpack\node_modules\tapable\lib\Tapable.js:60:69)
    at Compiler.emitAssets (node_modules\webpack\lib\Compiler.js:226:7)
    at Watching.<anonymous> (node_modules\webpack\lib\Compiler.js:54:18)
    at node_modules\webpack\lib\Compiler.js:403:12
    at Compiler.next (node_modules\webpack\node_modules\tapable\lib\Tapable.js:67:11)
    at Compiler.<anonymous> (node_modules\awesome-typescript-loader\dist\instance.js:275:9)

from memory-fs.

NicholasGWK avatar NicholasGWK commented on May 1, 2024

@ engageft3 Try logging the path and see what it is. For me the problem was my output path in webpack.config.js wasn't absolute, and had a ./build rather than build. But, the regex still had to be changed.

from memory-fs.

NicholasGWK avatar NicholasGWK commented on May 1, 2024

Worked around it by putting '/' at the beginning of my path in output for webpack config, causes it to think it's *nix

from memory-fs.

NicholasGWK avatar NicholasGWK commented on May 1, 2024

@stephenmathieson Yeah that workaround works for me, I think it address the path correctly in the in memory system. Reminder for anyone who reads this to only do this in the dev config, otherwise if you're on Windows the production webpack build with start writing to C:/build or similar :).

from memory-fs.

sokra avatar sokra commented on May 1, 2024

output.path must be an absolute value. This is also required by webpack.

from memory-fs.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.