An open API service for providing issue and pull request metadata for open source projects.

GitHub / jeffling/wallaby-webpack issues and pull requests

#33 - Error when webpack version is not supported

Pull Request - State: closed - Opened by smcenlly almost 5 years ago

#31 - fix: use fs.readFileSync instead of readFile for sync operation

Pull Request - State: closed - Opened by maksimr over 6 years ago

#30 - [Req] Better webpack typescript config support

Issue - State: closed - Opened by luchillo17 almost 7 years ago - 15 comments
Labels: more info is required

#29 - Vulnerable version of lodash

Issue - State: closed - Opened by luciavelasco about 7 years ago - 1 comment

#28 - Webpack 4 support

Issue - State: closed - Opened by edenworky over 7 years ago - 1 comment

#27 - including and rerunning tests

Issue - State: closed - Opened by pearljamik almost 8 years ago - 10 comments
Labels: more info is required

#26 - Wallaby not working with node express http module

Issue - State: closed - Opened by pearljamik almost 8 years ago - 21 comments
Labels: question, more info is required

#25 - http.IncomingMessage.prototype is undefined

Issue - State: closed - Opened by pearljamik about 8 years ago - 2 comments

#24 - Webpack 2

Issue - State: closed - Opened by gregorskii about 8 years ago - 6 comments
Labels: question

#23 - Wallaby webpack resolve.modules doesn't seem to resolve to modules.

Issue - State: closed - Opened by nathanvale over 8 years ago - 2 comments

#22 - Webpack target: 'node'

Issue - State: closed - Opened by timcosta over 8 years ago - 5 comments

#20 - updating to webpack@v2.2.0-rc.5 breaks wallaby tests

Issue - State: closed - Opened by pndewit over 8 years ago - 5 comments

#19 - webpack-wallaby now breaks in Webpack 2.1.0-beta.23+

Issue - State: closed - Opened by bfricka almost 9 years ago - 2 comments

#18 - No compile-time errors generated when testing Typescript.

Issue - State: closed - Opened by danimbrogno almost 9 years ago - 1 comment

#17 - Wallaby-webpack source code (out of sync and/or instrumentation) issue

Issue - State: closed - Opened by bZichett over 9 years ago - 6 comments

#16 - Graceful-fs deprecated for new node releases

Issue - State: closed - Opened by NickClark over 9 years ago - 1 comment

#15 - [help wanted] Problem to setup wallaby + webpack + babel

Issue - State: closed - Opened by Drathal almost 10 years ago - 4 comments

#14 - Best way to load specHelper?

Issue - State: closed - Opened by aaronjensen almost 10 years ago - 2 comments

#13 - using resolve.root for app code

Issue - State: closed - Opened by aaronjensen almost 10 years ago - 6 comments

#12 - Importing react throw error

Issue - State: closed - Opened by eskimoblood about 10 years ago - 2 comments

#11 - How to configure usage of webpack's raw-loader?

Issue - State: closed - Opened by RainerAtSpirit about 10 years ago - 1 comment

#10 - Added missing repository field

Pull Request - State: closed - Opened by hrmoller about 10 years ago - 2 comments

#9 - EntryModuleNotFoundError

Issue - State: closed - Opened by vjpr about 10 years ago - 4 comments

#8 - Runtime error: Error: Cannot find module "..." when ignoring modules with webpack.IgnorePlugin

Issue - State: closed - Opened by ArtemGovorov over 10 years ago - 1 comment
Labels: wontfix

#7 - ES6 import syntax not working in spec file

Issue - State: closed - Opened by okonet over 10 years ago - 5 comments
Labels: help wanted

#6 - `SyntaxError: Unexpected token` on spread attributes

Issue - State: closed - Opened by okonet over 10 years ago - 5 comments

#5 - Can not find modules resolved with resolve.fallback

Issue - State: closed - Opened by ArtemGovorov over 10 years ago
Labels: bug

#4 - testing

Issue - State: closed - Opened by jeffling over 10 years ago

#3 - caching

Issue - State: closed - Opened by jeffling over 10 years ago

#2 - Source maps

Issue - State: closed - Opened by jeffling over 10 years ago
Labels: bug

#1 - Tests don't run

Issue - State: closed - Opened by jeffling over 10 years ago
Labels: bug