Replies: 2 comments 2 replies
-
Thanks for filing! This warning is telling you that a dependency is written as TypeScript, which is unexpected. Most packages, even ones that were originally authored in TypeScript, should be published as JS so that everyone can use them. It sounds like you're already aware of that and that this is a custom package registry thing, but just wanted to explain for others. You can solve for this by adding an installer plugin to handle TypeScript. It looks like our docs on this are a bit out of date, but you can see an example here: https://www.snowpack.dev/#node-built-in-could-not-be-resolved For you, this would be:
This tells Snowpack to run your dependencies through this extra TS plugin. |
Beta Was this translation helpful? Give feedback.
-
I have the same situation as described in the original message: there are packages written in typescript that shared between projects using yarn workspaces. I am trying to figure out a way to import these packages into a snowpack-built app. I tried this, but it didn't work
|
Beta Was this translation helpful? Give feedback.
-
We have our package registry where we store just ts source files under namespace.
Today i try migrate from webpack to snowpack with
@snowpack/app-template-react-typescript
, but i stuck on errorLook like ts plugin ignore node_modules folder, even after i change in
tsconfig.json
this rulesAny ideas what I forgot?
Beta Was this translation helpful? Give feedback.
All reactions