Replies: 146 comments 17 replies
-
|
Awesome! Looking over the medium post and other docs and open issues, there are lot's of mentions of the deprecated |
Beta Was this translation helpful? Give feedback.
-
|
I don't think |
Beta Was this translation helpful? Give feedback.
-
|
Is |
Beta Was this translation helpful? Give feedback.
-
|
One early feedback: lots of exceptions seem to be eaten somewhere, which makes writing plugins a bit harder as you need to wrap them in try/catch statements to print them manually. I also noticed that the promise queue never seems to throw when one of the promises it contains fails, causing the program to exit as soon as the event loop is empty - and never waking up the promise queue. |
Beta Was this translation helpful? Give feedback.
-
|
You guys(@arcanis did, so mainly @hacknug and future other people) should probably create issues for those (bug) observations.
|
Beta Was this translation helpful? Give feedback.
-
|
Why |
Beta Was this translation helpful? Give feedback.
-
|
@JounQin because Parcel 2 supports multiple targets, the out dir needs to be set per target. You can do it by setting the {
"main": "foo/bar.js"
} |
Beta Was this translation helpful? Give feedback.
-
|
@devongovett I'm using parcel to build umd format |
Beta Was this translation helpful? Give feedback.
-
|
When i try to install it with npm |
Beta Was this translation helpful? Give feedback.
-
|
@scrossan-crown use |
Beta Was this translation helpful? Give feedback.
-
|
Should |
Beta Was this translation helpful? Give feedback.
-
|
@scrossan-crown |
Beta Was this translation helpful? Give feedback.
-
|
I'm getting this error when trying to run |
Beta Was this translation helpful? Give feedback.
-
|
@scrossan-crown It's probably related to #3413 so, since the other person hasn't yet made an issue in https://github.com/parcel-bundler/watcher, you probably could |
Beta Was this translation helpful? Give feedback.
-
|
@Banou26 I've opened an issue on watcher parcel-bundler/watcher#18 |
Beta Was this translation helpful? Give feedback.
-
|
Is it possible, or will it be possible to set the outDir? Right now I couldn't find anything else than using package.json to specify the output, or in some case this my not be enough. |
Beta Was this translation helpful? Give feedback.
-
|
The nightly build has |
Beta Was this translation helpful? Give feedback.
-
|
Hey y'all I'm having an issue with Sass.
$theme-colors: (
"primary": #8AFFA3,
);
@import "bootstrap/scss/bootstrap";But then when I try to build for production using Here is my <!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<title>Document</title>
<link rel="stylesheet" href="./App.scss">
</head>
<body>
<div id="root"></div>
<script src="./index.tsx"></script>
</body>
</html>Should I make an issue for this? |
Beta Was this translation helpful? Give feedback.
-
|
Did you find a solution? I'm having the same problem. |
Beta Was this translation helpful? Give feedback.
-
|
Is there way to hook into the bundle events in parcel 2? In v1 we had: const bundler = new Bundler(...);
bundler.on('bundled', (bundle) => {
// do your thing
});
bundler.bundle();I'm looking for this, while I'm working on a chrome extension. With I've tried the most obvious, but that didn't work: const parcel = new Parcel(config);
parcel.on('bundled', () => {});Awaiting the promise returned by either |
Beta Was this translation helpful? Give feedback.
-
const parcel = new Parcel({ /* ... */ })
const { unsubscribe } = await parcel.watch((err, build) => {
if (err) throw err
// ...
}) |
Beta Was this translation helpful? Give feedback.
-
|
@Banou26, awesome! That works! Thanks. Unexpected syntax though. |
Beta Was this translation helpful? Give feedback.
-
|
@Banou26, do you also know if there is an equivalent of the |
Beta Was this translation helpful? Give feedback.
-
|
@smeijer did you ever figure this out? |
Beta Was this translation helpful? Give feedback.
-
|
With parcel 2, react is complaining about dead code elimination.
Is there anything I should do? I've wrapped parcel in a small script, so I'm not using the cli: const Parcel = require('@parcel/core').default;
const getPort = require('get-port');
const parcel = new Parcel({
entries: ['src/index.html'],
distDir: 'dest',
port: 1234,
});
parcel.run(); |
Beta Was this translation helpful? Give feedback.
-
|
add |
Beta Was this translation helpful? Give feedback.
-
|
Hero! 🎉 That did the trick. const parcel = new Parcel({
entries: ['src/index.html'],
distDir: 'dest',
port: 1234,
mode: process.env.NODE_ENV === 'production' ? 'production' : undefined
});Even now I know of the |
Beta Was this translation helpful? Give feedback.
-
|
I wouldn't obviously expect this behavior, don't forget that this is the API you're using, not the CLI, imagine having your tool behavior changing because an user has x or y environment variables set instead of just passing flags. That'd be bad. |
Beta Was this translation helpful? Give feedback.
-
|
Also true. |
Beta Was this translation helpful? Give feedback.
-
|
Using 2.0.0-beta.1, I'm getting the following error: When added .parcelrc with the following content as instructed in migration guide, error changed to |
Beta Was this translation helpful? Give feedback.
-
|
Oh, the problem is that this |
Beta Was this translation helpful? Give feedback.
-
|
Thanks. I really don't think that should be necessary considering that there's no new default behavior that replaces raw import. |
Beta Was this translation helpful? Give feedback.
-
|
I tried this config in .parcelrc but got error: |
Beta Was this translation helpful? Give feedback.
-
|
Any thoughts on when the next beta will be published? globals in the alias section is a feature I'm particularly keen to use. I have things working but I'd like to move off nightly if I can. |
Beta Was this translation helpful? Give feedback.
-
|
Its been 2 months an around 200 commits since beta 1. A beta 2 would look good. |
Beta Was this translation helpful? Give feedback.
-
|
A beta 2 was released 15 days ago https://www.npmjs.com/package/parcel/v/2.0.0-beta.2 |
Beta Was this translation helpful? Give feedback.
-
Got error |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I'm trying to migrate from V1 to V2. I'm trying to do the same in V2 with the following code I'm running this in node and i am not able to get the build files written to the dist directory. |
Beta Was this translation helpful? Give feedback.
-
|
Using a custom package.json ...
"targets": {
"api-module": {
"distDir": "dist/api/module/",
"context": "browser",
"isLibrary": true,
"outputFormat": "esmodule",
"scopeHoist": true,
"sourceMap": true,
"source": "src/api/index.js"
}
}
...
> npx parcel build src/api/index.js
✨ Built in 1.08s
dist/index.js 35 B 87ms
Process finished with exit code 0When i remove the How are we supposed make builds with multiple custom targets? |
Beta Was this translation helpful? Give feedback.
-
|
All i can think of is this package.json ...
"targets": {
"api-module": {
"distDir": "dist/api/module/",
"context": "browser",
"isLibrary": true,
"outputFormat": "esmodule",
"scopeHoist": true,
"sourceMap": true
},
"api-browser": {
"distDir": "dist/api/browser/",
"context": "browser",
"isLibrary": true,
"outputFormat": "global",
"scopeHoist": true,
"sourceMap": false
},
"ui-module": {
"distDir": "dist/ui/module/",
"context": "browser",
"isLibrary": true,
"outputFormat": "esmodule",
"scopeHoist": true,
"sourceMap": true
},
"ui-browser": {
"distDir": "dist/ui/browser/",
"context": "browser",
"isLibrary": true,
"outputFormat": "global",
"scopeHoist": true,
"sourceMap": false
}
}
...
"scripts": {
"build": "npm run build:api-module && npm run build:api-browser && npm run build:ui-module && npm run build:ui-browser",
"build:api-module": "npx parcel build --target api-module src/api/index.js",
"build:api-browser": "npx parcel build --target api-browser src/api/index.js",
"build:ui-module": "npx parcel build --target ui-module src/ui/index.jsx",
"build:ui-browser": "npx parcel build --target ui-browser src/ui/index.jsx"
} |
Beta Was this translation helpful? Give feedback.
-
|
so it seems parcel has gone from zero config to much config? |
Beta Was this translation helpful? Give feedback.
-
|
Parcel 2 is a ground up rewrite with a plugin system in mind, so it does have quite a few breaking changes, there's a migration guide on the docs https://v2.parceljs.org/getting-started/migration/ In this case you can use |
Beta Was this translation helpful? Give feedback.
-
|
works now. Upgraded to current RC after fixing this. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I had a problem with |
Beta Was this translation helpful? Give feedback.
-
|
main section in |
Beta Was this translation helpful? Give feedback.
-
|
@FDiskas thank you for your help but in my situation, unfortunately, your solution doesn’t work. because I keep getting some errors like for my Recommended by parcel: |
Beta Was this translation helpful? Give feedback.
and others
-
We have just released Parcel 2
alpha 1alpha 2alpha 3beta 1beta 2beta 3 (yarn add -D parcel@next)!For a more bleeding edge version, use
yarn add -D parcel@nightly(published every midnight UTC).Please try it out and report any issues you find. If you'd like to contribute, we need help migrating over all of the remaining functionality from Parcel 1 (for example on these issues).
You can read more details in the announcement post (https://medium.com/@devongovett/parcel-2-0-0-alpha-1-is-here-8b160c6e3f7e) and the V2 Readme (https://github.com/parcel-bundler/parcel/blob/v2/packages/core/parcel/README.md).
To concentrate on Parcel 2, Parcel
1.x.xwill only receive bugfixes (and likely only critical ones).Please don't report bugs or feature requests here in the comments but open new issues instead.
Beta Was this translation helpful? Give feedback.
All reactions