-
Notifications
You must be signed in to change notification settings - Fork 983
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
Install dependencies into node_modules, not turbo_modules #333
Comments
How are you seeing this? From error stacktraces? Was meant to be an under-the-hood sort of thing for us, but understand why it's confusing if it bubbles up to the user |
You need to reference files from packages sometimes. See https://stackblitz.com/edit/js-whexau?file=index.html |
HTML and CSS (and JS really) can't use package names to reference resource. There are a number of cases where this comes up: |
@justinfagnani gotchya. StackBlitz was originally designed for projects that are using compilers/loaders/etc, so linking to node_modules in index.html isn't something we originally we planning to support. This is being changed in our bundler upgrade though, so you'll be able to link to node_modules in HTML files. ETA is end of month/early next 💪 |
You rock, thanks for all the improvements! |
@EricSimons awesome news! |
Will we be able to see node_modules files structure? when installing a dependency to node_modules we don't always know the path to the desired file, it would be awesome to see the file structure. Thanks a lot. |
This feature is now implemented in our new VS Code editor, available here! |
It's very unintuitive that dependencies are installed into turbo_modules. It took a while to even figure that out.
The text was updated successfully, but these errors were encountered: