[BUG] Disconcerting warnings and errors in blank Typescript template
See original GitHub issueBug Report Quick Checklist
- I am on the latest version of Snowpack & all plugins. (3.3.4)
- I use package manager yarn (Fill in: npm, yarn, pnpm, etc).
- I run Snowpack on OS macOS (Fill in: Windows, Mac, Linux, etc).
- I run Snowpack on Node.js v12+ (14.8.0)
Describe the bug
The blank Typescript template gives several warnings/error messages. This is disconcerting for people who are new to Snowpack, and just trying it out…
To Reproduce
Read the README.md for details, but the outline is:
npx create-snowpack-app test26mar --template @snowpack/app-template-blank-typescript --use-yarn
- see several deprecation warnings…
- s/3.0.1/3.3.4/ in
package.json
- Deprecations go away when re-running
yarn
yarn start
gives a Rollup preventAssignment error even though Rollup is not (obviously) being used
Expected behavior
No errors or warnings from the npx
or yarn start
commands
Anything else?
Demo repo and README.md at: https://github.com/richb-hanover/SnowpackTest-26Apr
Issue Analytics
- State:
- Created 2 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
[BUG] Disconcerting warnings and errors in blank Typescript ...
The blank Typescript template gives several warnings/error messages. This is disconcerting for people who are new to Snowpack, ...
Read more >TypeScript errors and how to fix them
Common Errors Below you find a list of common TypeScript errors along with the buggy code and its fixed version.
Read more >How to get rid of the warning .ts file is part of the TypeScript ...
app.json, and I would receive the error message for just about every new .ts file I added to the project. Explicitly adding the...
Read more >Improving TypeScript error handling with exhaustive type ...
Discover an improved method for handling errors in TypeScript that solves problems that arise from returning null and throwing try...catch.
Read more >Page 7 – All views and opinions are ... - Hosk's Dynamic Blog
Projects are a good example of past best practices being used. ... To diagnose an error, look at the error with an empty...
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 FreeTop 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
Top GitHub Comments
Thank you for tracking all these items down. I appreciate that effort. Your analysis makes sense
I am enough of a “techie” to see the power of Snowpack. And I can muddle through. But I also remain a “naive user”, and see the bumps along the road - these will slow its adoption. (That’s why I put “Disconcerting warnings…” in the title. They’re not necessarily bugs, but they make a newcomer wonder if something bad happened, or if, perhaps, the whole project is unreliable.)
I can see you’re deeply knowledgeable about the Javascript ecosystem and with the Snowpack environment. But it would take me far longer to reach those same conclusions. (And longer, still, to actually make any PRs.)
So I point out these problems a) to ask if I’m “doing it wrong” or b) to show where Snowpack could be improved. Is there a better (more helpful) place to make these observations? Could these reports be improved?
Many thanks.
The logs are in the README at: https://github.com/richb-hanover/SnowpackTest-26Apr and reproduced here…
Starting new Snowpack project
On 26 Apr 2021, use npx with a blank typescript template to create new project.
By default, this installs Snowpack 3.0.1. This generates the deprecated warnings (below).
Manually changing to Snowpack 3.3.4 in the package.json file removes these warnings. The project seems to run fine.
Using
yarn start
, see the second set (below) of Rollup warnings about preventAssignment even though the project doesn’t use Rollup.Error on initial start