-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rollup-plugin-vue@^4.0.1
compatibility
#78
Comments
If you want to work any debugging magic, you can clone the repo and install the latest rollup-plugin-vue. git clone [email protected]:alexsasharegan/vue-transmit.git
cd vue-transmit
npm i
npm i -D rollup-plugin-vue@^4.0.1
npm run build |
@alexsasharegan looks like vue plugin is supposed to generate a ts file, right? Could you try placing |
Tried that just now with ➜ vue-transmit git:(master) ✗ npm run build
> [email protected] prebuild /Users/alex/github.com/alexsasharegan/vue-transmit
> npm run clean
> [email protected] clean /Users/alex/github.com/alexsasharegan/vue-transmit
> scripts/clean.js
> [email protected] build /Users/alex/github.com/alexsasharegan/vue-transmit
> cross-env NODE_ENV=production rollup -c ./rollup.config.js
src/index.umd.ts → ./dist/vue-transmit.js...
[!] Error: Unexpected token
src/components/VueTransmit.vue.ts?rollup_plugin_vue=%7B%22type%22%3A%22script%22%2C%22lang%22%3A%22ts%22%7D (86:5)
84: import { DriverInterface, DriverConstructor } from "../core/interfaces";
85:
86: type FileSystemEntry = WebKitFileEntry | WebKitDirectoryEntry;
^
87:
88: export default Vue.extend({
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `cross-env NODE_ENV=production rollup -c ./rollup.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/alex/.npm/_logs/2018-05-07T16_54_41_779Z-debug.log |
Try modifying include filter for rpt2 to something like that: ( |
Now it cannot find the file: ➜ vue-transmit git:(master) ✗ npm run build
> [email protected] prebuild /Users/alex/github.com/alexsasharegan/vue-transmit
> npm run clean
> [email protected] clean /Users/alex/github.com/alexsasharegan/vue-transmit
> scripts/clean.js
> [email protected] build /Users/alex/github.com/alexsasharegan/vue-transmit
> cross-env NODE_ENV=production rollup -c ./rollup.config.js
src/index.umd.ts → ./dist/vue-transmit.js...
[!] (rpt2 plugin) Error: Could not find file: '/Users/alex/github.com/alexsasharegan/vue-transmit/src/components/VueTransmit.vue'.
src/components/VueTransmit.vue
Error: Could not find file: '/Users/alex/github.com/alexsasharegan/vue-transmit/src/components/VueTransmit.vue'.
at getValidSourceFile (/Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/typescript/lib/typescript.js:103163:23)
at Object.getEmitOutput (/Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/typescript/lib/typescript.js:103506:30)
at /Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/rollup-plugin-typescript2/src/index.ts:192:16
at TsCache.getCompiled (/Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/rollup-plugin-typescript2/src/tscache.ts:175:24)
at Object.transform (/Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/rollup-plugin-typescript2/src/index.ts:190:20)
at /Users/alex/github.com/alexsasharegan/vue-transmit/node_modules/rollup/dist/rollup.js:17316:48
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
at Function.Module.runMain (module.js:695:11)
at startup (bootstrap_node.js:188:16)
at bootstrap_node.js:609:3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] build: `cross-env NODE_ENV=production rollup -c ./rollup.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/alex/.npm/_logs/2018-05-07T18_28_09_072Z-debug.log For reference, here are the files:
|
I can't make your project build in my environment (win10, terminal or git bash).
And yeah, it works if I switch back to Maybe open a bug with |
I'll try and link this issue over there today or tomorrow. |
A little late, but I linked the issue at |
Such blocks are converted to virtual modules. For example: Typescript block in Test cases on fixture (https://github.com/vuejs/rollup-plugin-vue/blob/master/test/fixtures/with-script-typescript.vue) works fine with https://github.com/rollup/rollup-plugin-typescript. |
Hm, yes, looks like typescript is trying to load that file directly instead of requesting a snapshot from me for some reason. |
Any progress on this? The folks over on vuejs/rollup-plugin-vue#204 are curious if it's resolved. Is this an issue on their end, or here with the TS plugin? |
Sorry haven't looked at it in a while, I'll check again soon. |
@alexsasharegan ok, was much simpler than I thought, I was not returning updated list of cached modules to typescript, so it tried to find the module on its own. Should be fixed now, I'll make a release a bit later. |
I'm experiencing this in watch mode, but it happens randomly |
rollup-plugin-vue@^4.0.1
compatibility
What happens and why it is wrong
Prior to upgrading rollup-plugin-vue to v4, everything on https://github.com/alexsasharegan/vue-transmit was building okay. Upgrading to v4 generates an error in rpt2.
Terminal output
Versions
2.8.3
0.58.2
0.13.0
rollup.config.js
rollup.config.js
tsconfig.json
tsconfig.json
package.json
package.json
plugin output with verbosity 3
Output
The text was updated successfully, but these errors were encountered: