[Bugs] 0.5.2 breaking change: Path must be a string. Received undefined
See original GitHub issueDescription
I have been working on a coworker implementation that uses this plugin though I don’t really know about it except my coworker use to have it working.
Reproduction
https://travis-ci.org/yeutech-lab/rollup-umd-documentation/jobs/403153237#L1155
This guy helped me found the error: https://github.com/splunk/battlecat-poll/issues/3
Proposed solution
Downgrade to 0.5.1
:
$ npm uninstall babel-plugin-inline-react-svg --save-dev \
&& npm install babel-plugin-inline-react-svg@0.5.1 --save-dev
Issue Analytics
- State:
- Created 5 years ago
- Comments:18
Top Results From Across the Web
"Path must be a string. Received undefined" #144 - zkat/npx
After windows does some windows update, it breaks things. So I found that it is not running node as expected. Normally npx does...
Read more >node.js - TypeError: Path must be a string. Received undefined
I a persistent error while using serverless framework with serverless-offline and jest unit testing module.
Read more >Bug listing with status RESOLVED with resolution OBSOLETE ...
Bug :1523 - "[IDEA] Offload work by distributing trivial ebuild maintenance to users, introduce a simple stability voting system and have a core...
Read more >Changelog | Meteor API Docs
needs to use directly from npm the meteorjs/babel@7.16.1-beta.0. Breaking Changes. N/A. Migration Steps. Meteor Version Release. mongo@1.16.2 :.
Read more >Changes - Nginx.org
Bugfix: fixed break instruction in try-catch block. ... Change: returning undefined value instead of an empty string for ... Changes with njs 0.5.2....
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 Free
Top 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
v0.5.4 is released.
Thanks, that pinpointed it -
export const pkg = require(path.join(pkgBase, 'package.json'));
(ie, a dynamic require) broke it. I should be able to make a test case from that.