Comments (2)
Just thinking about this more (still trying to get the current tests running on my laptop), do you think it might be worthwhile having a look to have a common set of test cases and run the same ones for each bundler? Something like the following:
[vite, snowpack, nollup].forEach(engine => {
beforeEach(() => {
// start dev server
});
describe('some test case', () => {
it ('should update');
});
});
Would reduce a lot of duplication. Fixtures might have to be duplicated though because of different index.html
files though. Or do you think it would be better to keep tests separate for the time being?
from prefresh.
I think there's value in having a general test suite so we can test it all at once but it's going to be really hard to find the right abstraction to make all integrations work.
I do think that if we have like:
packages/
test/
fixtures/
webpack-dev-server/
nollup/
vite/
...
test.js
It could work (implemented in #165)
having some issues expanding into other suites but we're getting there #166
from prefresh.
Related Issues (20)
- @prefresh/vite (@prefresh/core) memory leak bug - "this.forceUpdate on an unmounted component" HOT 1
- Context value populated incorrectly when created using a helper function. HOT 2
- Implement SWC plugin HOT 3
- Update dependencies HOT 1
- Migrate to pnpm HOT 1
- Migrate to vitest HOT 1
- Consider deprecations
- useEffect cleanup triggering multiple times after updates? HOT 2
- HMR confuses global signals HOT 3
- Hot reloading doesn't work, the application is always fully reloading.
- Look into test flakiness
- Infinite re-rendering when using `webpack-hot-middleware` HOT 1
- `@prefresh/vite` types canβt be resolved when project uses modern TypeScript resolution modes
- No "exports" main defined in @prefresh/vite/package.json HOT 1
- webpack multicompile. hot-reload doesn't work
- Prefresh Webpack shouldn't assume the user is using NextJS HOT 1
- Memory leak when passing a signal content to a component props
- Package subpath './src/index.js' is not defined by "exports" in @prefresh\webpack\package.json
- prefresh-vite is not preserving the state of a component HOT 12
- Verify whether we can get rid of mapped-vnodes
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 prefresh.