Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / catamphetamine/webpack-isomorphic-tools issues and pull requests
#167 - Unexpected token less file
Issue -
State: closed - Opened by arman-mukatov over 3 years ago
- 6 comments
#166 - Tell webpack to add sources to JSON stats
Pull Request -
State: closed - Opened by willdurand almost 4 years ago
- 4 comments
#165 - Bump lodash from 4.17.10 to 4.17.15
Pull Request -
State: closed - Opened by dependabot[bot] over 5 years ago
- 2 comments
Labels: dependencies
#164 - docs: fix typo
Pull Request -
State: closed - Opened by Jason-Cooke over 5 years ago
- 1 comment
#163 - (/config/webpack-assets.json not found)
Issue -
State: closed - Opened by binyellow almost 6 years ago
- 1 comment
#162 - Babel 7 is not supported
Issue -
State: closed - Opened by idangozlan over 6 years ago
- 4 comments
#161 - Webpack resolve extensions not working with SSR
Issue -
State: open - Opened by priya-unacademy over 6 years ago
#160 - anyway to define __webpack_public_path__ or cdn?
Issue -
State: open - Opened by idangozlan over 6 years ago
- 15 comments
#159 - Upgrade for webpack 4
Pull Request -
State: closed - Opened by lemonCMS over 6 years ago
- 5 comments
#158 - mini-css-extract-plugin
Issue -
State: open - Opened by w567675 over 6 years ago
- 1 comment
#157 - Clarification in README
Issue -
State: closed - Opened by ghost almost 7 years ago
- 2 comments
#156 - Depreciation for webpack 4x
Issue -
State: closed - Opened by tavurth almost 7 years ago
- 2 comments
#155 - webpack-isomorphic-tools/plugin ReferenceError: window is not defined
Issue -
State: open - Opened by hrasekh about 7 years ago
- 11 comments
#154 - SyntaxError: Unexpected token < (skipping require call, fallback to original loader)
Issue -
State: closed - Opened by egorovli about 7 years ago
- 5 comments
#153 - Resolving webpack custom module paths
Issue -
State: closed - Opened by mnowotnik over 7 years ago
- 1 comment
#152 - Support for compression webpack plugin (js.gz)
Issue -
State: closed - Opened by hrishikhanapure over 7 years ago
- 1 comment
#151 - Inside CSS, background-url is packaged into absolute paths
Issue -
State: closed - Opened by ysk2014 over 7 years ago
- 1 comment
#150 - Ability to specify publicPath at runtime for server-side?
Issue -
State: closed - Opened by biddlem over 7 years ago
- 1 comment
#149 - Ability to ignore warnings / errors
Issue -
State: closed - Opened by RaulTsc over 7 years ago
- 6 comments
#148 - Keep getting errors module not defined and exports not defined
Issue -
State: closed - Opened by ghost over 7 years ago
- 9 comments
#147 - webpack_asset_path is not defined
Issue -
State: closed - Opened by kikoanis over 7 years ago
- 3 comments
#146 - Is it possible to have _style property in production using ExtractTextPlugin loader
Issue -
State: closed - Opened by rolele over 7 years ago
- 2 comments
#145 - Error while wepback build
Issue -
State: closed - Opened by lu911 over 7 years ago
- 2 comments
#144 - Seems like my webpack.config.js file is getting ignored
Issue -
State: closed - Opened by danazkari over 7 years ago
- 1 comment
#143 - Error: More than a single candidate module was found in webpack stats for require()d path "!!..
Issue -
State: open - Opened by fisherw over 7 years ago
- 2 comments
#142 - Not compatible with webpack 3
Issue -
State: closed - Opened by damien916 over 7 years ago
- 3 comments
#141 - Module did not self-register & webpack-assets.json for production is weird
Issue -
State: closed - Opened by rolele over 7 years ago
- 7 comments
#140 - getting window error when trying to import scss from node_module
Issue -
State: closed - Opened by idangozlan over 7 years ago
- 5 comments
#139 - when webpack-hot-middleware hot reload page,but the assets is webpack-assets.json is null
Issue -
State: closed - Opened by sponia-joker almost 8 years ago
- 5 comments
#138 - Issue loading multiple css files
Issue -
State: closed - Opened by reidblomquist almost 8 years ago
- 2 comments
#137 - Webpack 2 loading scss with asset not found error
Issue -
State: closed - Opened by fatstar415 almost 8 years ago
- 4 comments
#136 - Dose tool support webpack 2?
Issue -
State: closed - Opened by kuongknight almost 8 years ago
- 1 comment
#135 - Incremental build slowdown
Issue -
State: closed - Opened by nasushkov almost 8 years ago
- 5 comments
#134 - Error: Cannot find module './convert-source-map'
Issue -
State: closed - Opened by wellyshen almost 8 years ago
- 6 comments
#133 - webpack-assets lifecycle
Issue -
State: closed - Opened by eseom almost 8 years ago
- 1 comment
#132 - Question regarding to chunk for code splitting
Issue -
State: closed - Opened by hung-phan almost 8 years ago
- 9 comments
#131 - CommonsChunkPlugin manifest load error
Issue -
State: closed - Opened by elevensky about 8 years ago
- 2 comments
#130 - Unexpected token >
Issue -
State: closed - Opened by eddievagabond about 8 years ago
- 6 comments
#129 - Isomorphic tools for multiple dev servers?
Issue -
State: closed - Opened by arasmussen about 8 years ago
- 1 comment
#128 - ExtractTextPlugin 2.0.0-rc.2 with `allChunks: true` and `require.ensure` not creating production asset stats
Issue -
State: closed - Opened by dtothefp about 8 years ago
- 2 comments
#127 - css-load problem
Issue -
State: closed - Opened by 2637309949 about 8 years ago
- 3 comments
#126 - added support for querystring in filenames
Pull Request -
State: closed - Opened by pmdroid about 8 years ago
- 6 comments
#125 - Update README.md
Pull Request -
State: closed - Opened by wmyers about 8 years ago
- 5 comments
#124 - [npm link] Possibly can't find NPM linked node_modules
Issue -
State: open - Opened by maerzhase about 8 years ago
- 2 comments
#123 - Explain how to make SSR
Issue -
State: closed - Opened by yoihito about 8 years ago
- 1 comment
#122 - webpack-assets.json content becomes wrong on subsequent builds in watch mode
Issue -
State: closed - Opened by vjancik about 8 years ago
- 1 comment
#121 - Cannot load SVG as React Component
Issue -
State: closed - Opened by seleckis about 8 years ago
- 14 comments
#120 - Babel Runtime.
Issue -
State: closed - Opened by tom-drake over 8 years ago
- 5 comments
#119 - Module not found: Error: Cannot resolve module 'fs'
Issue -
State: closed - Opened by lewis617 over 8 years ago
#118 - Broken fragment url in README.md
Pull Request -
State: closed - Opened by vankhoawin over 8 years ago
- 2 comments
#117 - Sync-request
Issue -
State: closed - Opened by mihirsoni over 8 years ago
- 4 comments
#116 - Webpack hot reloading failed due to the error of webpack-isomorphic-tools
Issue -
State: closed - Opened by wellyshen over 8 years ago
- 2 comments
#115 - `require` doesn't seem to work properly on server.
Issue -
State: closed - Opened by kevinmartin over 8 years ago
- 4 comments
#114 - [webpack-isomorphic-tools] [error] `.development()` method is now deprecated
Issue -
State: closed - Opened by Iuriy-Budnikov over 8 years ago
- 16 comments
#113 - ERROR in (webpack)-isomorphic-tools/package.json
Issue -
State: closed - Opened by peter-mouland over 8 years ago
- 9 comments
#112 - webpack-assets.json with undefined host
Issue -
State: closed - Opened by brenodouglas over 8 years ago
- 6 comments
#111 - In prod mode with ExtractTextPlugin, my styles import returns an array of values.
Issue -
State: closed - Opened by shouvik over 8 years ago
- 10 comments
#110 - Stuck requiring assets
Issue -
State: closed - Opened by shouvik over 8 years ago
- 2 comments
#109 - _webpackIsomorphicTools2.default.assets is not a function and missing path with webpack-isomorphic-tools.assets()
Issue -
State: closed - Opened by ChazUK over 8 years ago
- 8 comments
#108 - Never reaches following code every second time
Issue -
State: closed - Opened by Yuripetusko over 8 years ago
- 19 comments
#107 - JSX compiling error `Unexpected token <`
Issue -
State: closed - Opened by evgenosiptsov over 8 years ago
- 7 comments
#106 - [webpack-isomorphic-tools] [error] asset not found
Issue -
State: closed - Opened by garbin over 8 years ago
- 7 comments
#105 - would provide a link to my example project?
Issue -
State: closed - Opened by peter-mouland over 8 years ago
- 6 comments
#104 - React is not defined
Issue -
State: closed - Opened by peter-mouland over 8 years ago
- 6 comments
#103 - global.webpack_isomorphic_tools creates an error on mocha
Issue -
State: closed - Opened by mateeyow over 8 years ago
- 5 comments
#102 - Webpack_isomorphic_tools_plugin.style_loader_filter isn't compatible with latest-version npm
Issue -
State: closed - Opened by dayzhou over 8 years ago
- 2 comments
#101 - Can not get .scss object on client side
Issue -
State: closed - Opened by ghost over 8 years ago
- 2 comments
#100 - Asset not found scss
Issue -
State: closed - Opened by Arueilen over 8 years ago
- 4 comments
#99 - Add option to disable all stats output of the plugin
Pull Request -
State: closed - Opened by danez over 8 years ago
- 3 comments
#98 - Unable to split a module from the main bundle when using with webpack "require.ensure".
Issue -
State: closed - Opened by jboonmee over 8 years ago
- 3 comments
#97 - links are dead :(
Issue -
State: closed - Opened by damienleroux over 8 years ago
- 1 comment
#96 - 'Cannot find module' when using webpack loaders
Issue -
State: closed - Opened by edorivai over 8 years ago
- 13 comments
#95 - README typo fixes
Pull Request -
State: closed - Opened by jetpacmonkey over 8 years ago
- 1 comment
#94 - ProvidePlugin for automatic global variable importing
Issue -
State: closed - Opened by alecperkey over 8 years ago
- 5 comments
#93 - How to test the component that use this tools?
Issue -
State: closed - Opened by lewis617 over 8 years ago
- 6 comments
#92 - [Feature proposal] Use MemoryFS instead of disk filesystem
Issue -
State: closed - Opened by peter-mouland over 8 years ago
- 6 comments
Labels: enhancement, wontfix
#91 - Changing relative path of webpack-assets
Issue -
State: closed - Opened by mmahalwy over 8 years ago
- 1 comment
#90 - update
Pull Request -
State: closed - Opened by bartekus over 8 years ago
- 4 comments
#89 - putting chunkhash as parameter in output filename cause javascript assets to be empty
Issue -
State: closed - Opened by eladlevy over 8 years ago
- 4 comments
#88 - Objects are not valid as a react child
Issue -
State: closed - Opened by vpanjganj over 8 years ago
- 1 comment
#87 - Do I have to reload my server process on every build?
Issue -
State: closed - Opened by ignatevdev over 8 years ago
- 1 comment
#86 - "React attempted to reuse markup in a container but the checksum was invalid" when using require.ensure
Issue -
State: closed - Opened by olalonde over 8 years ago
- 1 comment
#85 - Можно самый простой пример реализации?
Issue -
State: closed - Opened by borm over 8 years ago
- 1 comment
#84 - require.ensure ?
Issue -
State: closed - Opened by loudwinston over 8 years ago
- 4 comments
#83 - Can't use imports-loader with webpack-isomorphic-tools
Issue -
State: closed - Opened by jvorcak over 8 years ago
- 3 comments
#82 - How to use this with post-css?
Issue -
State: closed - Opened by lewis617 over 8 years ago
- 2 comments
#81 - Failing to load images and styles
Issue -
State: closed - Opened by papigers over 8 years ago
- 12 comments
#80 - Consider using a naming convention more "Javascripty"
Issue -
State: closed - Opened by romulof over 8 years ago
- 1 comment
#78 - Assets not found issue with React-Toolbox. Please help. Tried everything I can.
Issue -
State: closed - Opened by shakalakatechie almost 9 years ago
- 9 comments
#75 - webpack 2 support?
Issue -
State: closed - Opened by mmahalwy almost 9 years ago
- 5 comments
#71 - webpack-assets.json not found
Issue -
State: closed - Opened by kiki-le-singe almost 9 years ago
- 10 comments
#68 - Fix break: use regexp to detect css-loader
Pull Request -
State: closed - Opened by kouhin almost 9 years ago
- 33 comments
#66 - Resolving scss in node_modules
Issue -
State: closed - Opened by isaac-peka almost 9 years ago
- 9 comments
#45 - Reasoning behind stats info always being output to the console
Issue -
State: closed - Opened by tanem about 9 years ago
- 22 comments
#40 - "asset not found" Error while file is present in webpack-assets.json
Issue -
State: closed - Opened by happypoulp about 9 years ago
- 18 comments
#39 - Setting up initial cache before starting the server
Issue -
State: closed - Opened by mwildehahn about 9 years ago
- 10 comments
#38 - Relative paths on require() call don't match the values in webpack-assets.json
Issue -
State: closed - Opened by sergesemashko about 9 years ago
- 13 comments
#25 - Include styles in stats extracted by ExtractTextPlugin
Issue -
State: closed - Opened by dtothefp over 9 years ago
- 15 comments
#4 - [error] asset not found: ./node_modules/font-awesome/css/font-awesome.css
Issue -
State: closed - Opened by tomatau over 9 years ago
- 36 comments
#3 - Style: snake_case vs camelCase
Issue -
State: closed - Opened by johanneslumpe over 9 years ago
- 12 comments