2.2.2 requires glamor
See original GitHub issueJust updated react-toastify
to 2.2.2
from npm and it broke my build:
ERROR in ./node_modules/react-toastify/lib/ProgressBar.js
Module not found: Error: Can't resolve 'glamor' in '/home/.../node_modules/react-toastify/lib'
@ ./node_modules/react-toastify/lib/ProgressBar.js 17:14-31
@ ./node_modules/react-toastify/lib/Toast.js
@ ./node_modules/react-toastify/lib/ToastContainer.js
@ ./node_modules/react-toastify/lib/index.js
@ ./lib/.../action/notificationsactions.js
@ ./lib/.../action/notificationsactions_test.js
@ ./testfiles/unit_tests.js
webpack: Failed to compile.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
FFXIV 2.2 0310 Glamours System Unlock Quest - YouTube
Glamours cannot be cast Casting the glamour of a hooded cowl on a robe, ... The equipment requirements of a glamoured item are...
Read more >glamor - npm
Start using glamor in your project by running `npm i glamor`. There are 512 other projects in the npm registry ... 2.2.2 •...
Read more >r/ffxiv - This is how the glamour system was first implemented ...
These days I'd say micromanaging anything in a game needs to be a specific design choice for a good thematic reason or otherwise...
Read more >Glamours - Final Fantasy XIV A Realm Reborn Wiki
The glamour system can be used on all gear the same or lower equipment level than your current gear. After using a glamour...
Read more >module.exportDefault is not a function - help - Meteor forums
... },"Router.js":function module(require,exports,module){ ... meteor-base@1.4.0 # Packages every Meteor app needs to have ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
sorry guys I’ll fix it asap. You could upgrade to the v3
Indeed, since v3 I switched to glamor so no need to import the css. I’ll check if there is a way to add deprecation notice when npm update the package.