You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 18, 2022. It is now read-only.
import statments inside the SFC <script> area should be correctly resolved during a rollup rebuild triggered by the rollup-watch
Actual behavior
import statments inside SFC <script> area is failed to be resolved.
Steps to reproduce the behavior
use the cookbook/minimal example as the base.
add any valid import statement in the <script> area of MyComponent.vue
let's say that the package imported is called my-package and assume that it is correctly installed inside node_modules.
run npx rollup -c -w
it succeeds
make any trivial but valid chagnes to the MyComponent.vue and SAVE it
rollup rebuilds the example but fails with Error: Could not load my-package (imported by /path/to/the/example/MyComponent.vue?rollup-plugin-vue=script.js): ENOENT: no such file or directory, open 'my-package'
The text was updated successfully, but these errors were encountered:
nandin-borjigin
changed the title
cant resolve imports inside <script> tag when re-building by watch mode
import statments inside <script> tag is failed to be resolved when re-building by watch mode
Sep 18, 2018
Expected behavior
import statments inside the SFC
<script>
area should be correctly resolved during a rollup rebuild triggered by therollup-watch
Actual behavior
import statments inside SFC
<script>
area is failed to be resolved.Steps to reproduce the behavior
cookbook/minimal
example as the base.<script>
area ofMyComponent.vue
let's say that the package imported is called
my-package
and assume that it is correctly installed inside node_modules.npx rollup -c -w
MyComponent.vue
and SAVE itError: Could not load my-package (imported by /path/to/the/example/MyComponent.vue?rollup-plugin-vue=script.js): ENOENT: no such file or directory, open 'my-package'
The text was updated successfully, but these errors were encountered: