Comments (2)
Why are there two branches actually? Wouldn't it be easier to maintain if there were two config files and a commandline param to choose which one you want to use?
Then people could try out both or so
from sapper-template.
It wouldn't just be a matter of two config files - there would also be differences in the package.json
dependencies. And also we want people to make changes to their bundler configs in their projects if they need additional plugins or other special handling or whatever. Would the other config still be living in their project all this time, not in sync with the one they're using?
It seems simplest to me to just present two complete and (from the consumer's point of view) independent project starters - which also makes it clearer to them that if they decide to switch bundlers at some point, it's pretty clear that they're going to have some manual migration to do.
If the two branches are automatically built from one common branch, that's not really a maintenance lift for the sapper-template
repo. And consumers would be getting what they're getting now: two branches, which I think is better for them than a single branch.
from sapper-template.
Related Issues (20)
- Set start_url in manifest.json correctly
- How to publish a production site to run in an external HTTP server like Nginx? HOT 1
- npm run export error: Cannot find module sapper HOT 1
- Cannot use import statement outside a module HOT 9
- Include setupTypeScript script only in Rollup branch
- DRY out default Webpack config
- Svelte-check returns error "Cannot find module" on image import when using TypeScript HOT 2
- "Cannot use namespace 'Preload' as a type" error when typing preload function HOT 7
- Error: Unexpected character '�' (Note that you need plugins to import files that are not JavaScript) HOT 5
- Module '"*.jpg"' can only be default-imported using the 'allowSyntheticDefaultImports' flag
- Sapper Typescipt, can't spin up dev server HOT 4
- Page doesn't load. A ServiceWorker passed a promise to FetchEvent.respondWith() that rejected with ‘TypeError: NetworkError when attempting to fetch resource
- css sourcemap broken HOT 1
- sapper export to electron, broken paths
- Service worker warns: No directory provided. Skipping CSS generation HOT 11
- Types in latest Sapper incompatible with Express HOT 1
- Bug: Rollup plugin-replace: preventAssignment set to "false" HOT 11
- Getting started tutorial: Live reload not working HOT 3
- Upgrade webpack template to use svelte-loader 3.0.0 HOT 3
- Type errors after converting to TypeScript HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from sapper-template.